OPEN SOURCE / PRACTICAL ENGINEERING
Your agent wrote 10,000 lines.
You still have to review them.
AI made writing code easier. It didn't remove your responsibility for what reaches production. Maybe your agent hit its usage limit, or a "small" ticket grew after you started coding. Start with the problem — then find a workflow and the tools to use it.
One human responsible for the result.
# assume the diff is fine# flag what still needs a human checkdef review(change: Change) -> None: for assumption in change.assumptions: if not assumption.verified: raise ReviewRequired( "Verify before shipping" )/guides 01 / START WITH THE PROBLEM
Where are you losing time?
You don't need to know which tool or skill to install. Start with what keeps getting in your way.
Your agent wrote 10,000 lines. You still have to review them.
It's hard to keep the whole change in your head. What if you miss a production bug — or your teammate spots an obvious mistake and wonders whether you reviewed the AI's work at all?
Why do you have to babysit your AI agent through every task?
You know what good code and writing look like. But unless you keep correcting the agent, it doesn't work to your standards — and you can't trust it to get the details right on its own.
Your agent hit its usage limit. You're not even done.
You burn through tokens before the work is finished. How can you avoid hitting the limit so quickly — or continue in another tool without losing the context you need?
You said the ticket would take two days. Now it’s day five.
Hidden requirements made the task bigger than anyone expected. Now you're late — and worried the person waiting for it thinks you're slow, rather than realizing the estimate was wrong.
You built it. Only to realize it was the wrong thing and you have to start over.
You don't know who to ask, they're unavailable, or even writing the Slack message feels awkward. Guessing is easier in the moment, until the answer arrives and your work needs redoing.
These are the problems being explored. Full guides will link to X or LinkedIn once published.
/tools 02 / USE THE WORKFLOW
Skip the research. Use what's already working.
Once you know what helps, you shouldn't have to find, install, and configure every tool yourself.
dotfiles.
Get tools, shortcuts, and agent configurations I've already researched and set up — without spending hours finding, installing, and troubleshooting every piece yourself.
View the repositoryFind the workflow. Follow the setup guide. Get back to work.
SystemSmith
Teach your agent what matters before it starts coding: clear scope, checked assumptions, reviewable changes, and engineering standards.
GITHUB REPOSITORY →SkillPort
Install reusable agent skills where you need them, without manually moving files between tools and projects.
GITHUB REPOSITORY →/hire-me 03 / FOR HIRING TEAMS
Need another engineer on your software team?
See the projects, technical decisions, and professional background behind the tooling.
/hire-me/beyond-the-keyboard 04 / PERSONAL SYSTEMS
Where is your day costing you?
What you do before and after work affects your energy, focus, and delivery. Explore practical routines and systems for getting more from your 24 hours.
/beyond-the-keyboardSTAY IN TOUCH
Have a specific problem worth solving?
Follow the public work on GitHub, or get in touch if you want to discuss an engineering workflow.