For practising software engineers
Turn experiments into dependable engineering.
I build systems, test how they behave, and share what I learn so you can apply it in your own work.
From the working notes
Build it. Understand it. Explain it.
What did I learn?
What evidence supports it?
Where can someone else apply it?
Start with a question
01 / Experiment
What should I test before committing?
Explore an idea, question the assumptions, and find evidence that helps you decide.
02 / Build
How do I build a useful, efficient system?
Architecture, implementation, performance, and the trade-offs behind a working solution.
03 / Improve
How do I make the practice dependable?
Testing, delivery, technical leadership, and making hard-won learning reusable.
Latest articles
How I Run Multiple Engineering Workstreams in the GitHub Copilot App
How I Run Multiple Engineering Workstreams in the GitHub Copilot App
Read More
The Safest AI Agent Knows When to Say No
The Safest AI Agent Knows When to Say No
Read More
What is a Solutions Architect (and how can you become one)?
What is a Solutions Architect (and how can you become one)?
Read MoreOn my workbench right now
Putting AI to practical use.
My current experiments involve prompting, agents, orchestration, and evaluating whether their results are fit for purpose.
How I Run Multiple Engineering Workstreams in the GitHub Copilot App
How I Run Multiple Engineering Workstreams in the GitHub Copilot App
The Safest AI Agent Knows When to Say No
The Safest AI Agent Knows When to Say No
The engineer behind the explanations
Hi, I’m James.
I’m a senior software engineer at Microsoft. Hands-on work gives me something substantive to share. Explaining it exposes gaps and sharpens my understanding.
Keep learning with me.
Read the explanations, explore the code, and follow along on YouTube.