Fitness for purpose: taking risks with quality
When product teams obsess over perfect quality, they risk standing still, but by embracing a 'fit for purpose' mindset and planning for instability, they can move faster and smarter.
Code quality and design
71 posts
These questions will be answered after technical due diligence
Investing without technical due diligence is like buying a used car without opening the bonnet. This article demystifies the audit process, shares what red flags we look for, and explains why investors should care deeply about code, processes and product.
What would it cost to rebuild this software from scratch?
Evaluating the cost of rebuilding software from scratch involves more than counting development hours; it requires recognising the invisible value of user feedback, lessons learned, and embedded experience.
AI writes bad code, but what if that’s the good news?
Should engineers fear messy AI code or embrace it as a tool for fast product validation? This story reveals why your cleanest code might not be your most valuable contribution. Why founders will use AI generated code more and more for MVPs and prototyping and why engineers should embrace this.
Another early-stage SaaS founders dilemma: buy a pre-built app or build one from scratch
Should SaaS founders buy or build their MVP? We compare pre-built apps vs custom development across cost, time, scalability, and code quality — so you can choose the right foundation for your product.
🌶️ SaaS startups should never use microservices. Like, never-ever.
Many SaaS startups over-engineer their architecture with microservices. Here's why that's usually a costly mistake—and what to do instead.
The hidden cost of API migrations
Forced API migrations without a rollback plan? That’s how businesses lose trust—and money.
Taming a Python: don't let the snake bite
Adapting to a new tech stack is all about mindset. Switching from PHP to Python was an eye-opener. Package management confusion, unexpected paradigms, and a lack of encapsulation made for an interesting challenge. Embracing constraints is the secret to growth.
Learning from OSS: legacyBehaviour property on Next.js 's Link component
Ever introduced a breaking change and instantly regretted it? Components evolve, but forcing users into painful refactors isn’t ideal. Next.js tackled this with a legacyBehaviour flag—letting devs opt out of the new behavior while they migrate at their own pace.