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?
Team and leadership content by madewithlove. Helping SaaS startups and scale-ups build teams and software. Welcome to our knowledge base.
What can investors do about legacy code to prevent your startup from failure? What is the difference between legacy and technical debt?
What can theatre teach startups about silos? That rehearsed collaboration beats chaos every time. madewithlove supports SaaS companies with CTO coaching, audits, and software engineering: discover how to keep your teams working together at the heart of your business.
Building diverse tech teams takes more than good intentions. From job ads and interviews to flexible work and international hiring, discover how we try to embed inclusion into every stage of the hiring process, subtly, sustainably, and deliberately.
As AI becomes a standard part of every developer’s toolkit, tech hiring needs to evolve from policing its use to understanding how candidates apply, evaluate, and collaborate with it.
Claude can now test your frontend. With a bit of config, the Playwright MCP server lets Claude run browser tests, find bugs, and even generate reusable test code. This could be a game-changer for startups without QA.
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.
Offboarding is a crucial part of security. Forgotten accounts and overlooked credentials can expose your systems to risk. This post offers real examples, a checklist approach, and clear steps to make offboarding more reliable across teams.
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.
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.