Team and leadership content by madewithlove. Helping SaaS startups and scale-ups build teams and software. Welcome to our knowledge base.
Micromanagement rarely starts with bad intent. It usually starts with silence. When nobody knows what you are working on, meetings multiply, trust erodes, and focus disappears. This piece shows how clear, boring communication is your best defence.
Hiring to fix velocity often multiplies your problems. Reduce avoidable mistakes first: tighten decision-making, align product and engineering, and put foundations in place that make a small team dangerous in the right way.
Outages can strike unexpectedly, impacting businesses and users alike. In this episode of the SaaS Show, hosts Andreas and Sjimi delve into the recent outages experienced by major cloud providers like Amazon and Cloudflare.
Of course your product is AI-based. There is no need mention this anymore. Tech loves a fashionable label. Web 2.0 had its moment, then mobile, then the cloud. Do not tell me your product uses AI. Tell me what your product can do that was impossible before AI existed.
Outdated myths about developers—like “they hate meetings” or “only care about code”—create friction, missed context, and rework. Learn how to build healthier collaboration across engineering and product.
Building a thriving remote-first culture takes more than allowing people to work from home. Discover how hiring for ownership, embracing asynchronous work, and saying no to misaligned projects creates a sustainable remote future.
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.
AI is not replacing developers, but it is replacing developers who refuse to use it. The real skill lies in how well you steer, validate, and challenge the model. Fundamentals matter, but today’s best engineers treat AI as an amplifier, not a crutch.
What can investors do about legacy code to prevent your startup from failure? What is the difference between legacy and technical debt?