Replicate before you report
· 6 min readA bug report nobody has reproduced is only a rumour, whether a person or an agent wrote it. Here's the rule my team adopted, and the bug that proved it.
A bug report nobody has reproduced is only a rumour, whether a person or an agent wrote it. Here's the rule my team adopted, and the bug that proved it.
I started with one agent. Here's how that became dedicated roles, and a testing path that starts with the spec, before anyone builds.
Treat AGENTS.md as onboarding for coding agents. Keep commands, conventions and project decisions current so each new session starts with useful context.
I stopped treating AI as one chat window and started treating it like a small team, with lanes, handoffs and a review gate. Here's how that works day to day, and what still needs me.
Storyblok billed us thousands in breach fees. We moved our sites off it in hours. AI made exit cheap. Lock-in is a worse bet than looking after customers.
We now generate code faster than we can reliably review it. Practical principles for reviewing AI-generated pull requests without slowing your team down.
Obsessing over clean code dogma can actually slow your team down. Here's what to focus on instead.
I have recently gotten my AWS Certified Solutions Architect - Associate certificate. In this post, I will share how I prepared for the exam and hopefully it helps you to get certified.