I care about practical systems, AI-assisted workflows, Linux, backend engineering, infrastructure, and tools that help people execute better. I am interested in collaborating with technical people who value clarity, responsibility, and building things that actually work.
Better execution as a theme
The thread through everything I do is execution. Ideas are abundant. The ability to turn an idea into something that runs, stays running, and helps someone is rare. I want to be on the side of execution: building systems that are boringly reliable and quietly useful.
That means choosing tools that are well understood over tools that are new. It means documenting decisions so they survive context switches. It means caring about the handoff as much as the initial build.
AI-assisted workflows
I use AI tools daily for code review, drafting, summarisation, and exploring unfamiliar codebases. The value is not in generating large amounts of code. The value is in reducing the friction of starting: getting past the blank page, catching issues before they reach review, and reframing problems when I am stuck.
- AI review catches patterns I would miss after hours of focus
- Drafting with AI produces structure that I then edit heavily
- Exploration with AI reduces the time to understand an unfamiliar project
The caveat is the same as any tool: garbage in, garbage out. AI accelerates both good thinking and bad thinking. Review is not optional. It is the step that makes the tool useful instead of dangerous.
The kind of collaboration I want
I want to work with people who take their craft seriously but not themselves. People who can argue about architecture without making it personal. People who ship, document, and iterate.
- Clarity over cleverness
- Responsibility over ownership
- Building things that actually work over building things that sound impressive
What is next
This site is part of that direction. The blog will grow as the work does. Topics will come from real delivery: backend systems, infrastructure decisions, AI workflow experiments, and the lessons that only surface after something breaks.
If any of this resonates, reach out. I am open to collaboration, conversation, and projects that need someone who cares about execution.