The hidden cost of multiple repositories
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
Code quality
90 posts
A guide to vibe coding vs AI-assisted development
Vibe coding or AI-assisted development? The choice isn't binary, but getting it wrong at the wrong stage will cost you. This piece breaks down when to embrace speed over architecture, when to take back control, and why the best teams don't pick sides.
The value of code review
Code reviews improve more than code quality. Done well, they shape better problem-solving, expose edge cases, and spread knowledge across teams. Learn how small, focused reviews and AI support help teams ship faster with confidence.
Getting started with performance testing
Performance bugs erode trust quietly until users explode. Three pragmatic steps help you catch slowdowns early: explore real bottlenecks with Sentry, test with production-sized data, and add lightweight API load tests.
Analyse your tables for better performance
I recently encountered a issue with MySQL query performance. A particular query would perform very badly in production, but perform very well in the testing environments.
No designer? No problem with v0
For small teams without a designer, v0 is a game-changer. The cost justifies itself by letting you explore and validate ideas in minutes rather than days.
The stainless steel lesson: why boring technology outlasts shiny frameworks
Shiny frameworks promise magic, but like cheap non-stick pans, they scratch, peel, and end up in the bin. Boring technology, like stainless steel, isn’t sexy, but it lasts for decades if treated well. The lesson? Build for the long haul, not the quick thrill.
Legacy vs technical debt: how investors can spot hidden risks in software products
What can investors do about legacy code to prevent your startup from failure? What is the difference between legacy and technical debt?
Ignoring revisions when using git blame
Tired of git blame pointing to useless formatting commits? Learn how to ignore revisions with --ignore-rev or .git-blame-ignore-revs to keep Git history accurate and helpful.