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?
66 posts
Your next hire will use AI in their technical test. Obviously.
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.
Technical due diligence is broken: going beyond the checklist
Most technical due diligence audits focus on code quality and tooling, but the real risk lies in invisible processes, fragile teams, and product chaos, which is why madewithlove audits the full stack of your organisation, from code to culture.
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.
The enshittification of the internet: are you building value or friction?
AI agents shouldn’t become CAPTCHA solvers: discover how monetisation-driven UX patterns have turned the web into a hostile environment and what honest design can do to reverse the trend.
5 red flags for VCs when planning to invest in Seed or Series A companies
Discover the five most common technical-due-diligence red flags—from undersized or misaligned teams to “just-about-working” codebases—that VCs must spot before writing a cheque.
Making an impact by combining our services
Madewithlove combines interim CTOs and staff engineers to help SaaS scale-ups align strategy with execution and build resilient tech teams.
Why involving engineers in product meetings saves time and money
Involving engineers in product specification meetings reduces costly iterations and accelerates feature launches for SaaS startups.
Should we really ship fast and break things?
Should startups test everything before shipping? We break down how to balance testing with product velocity—and why 100% coverage is often the wrong goal.