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?
Code quality and design
65 posts
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.
A Rubber Duck’s Guide to Better Engineering: Part 2
Professor Quacks is back with five more principles for better engineering: build tools that help, move with healthy urgency, plan wisely, work well with others, and lead by example. These aren’t just coding tips, they’re culture-shaping lessons.
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.
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.