The hidden cost of multiple repositories
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
LLMs generate code on demand, but they do not replace maintainers, communities, or years of shared learning. This piece explores how AI-assisted coding risks fragmenting logic, increasing technical debt, and slowly eroding the open source ecosystem.
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.
Performance bugs erode trust quietly until users explode. Three pragmatic steps help you catch slowdowns early: explore real bottlenecks with Sentry, test with production-sized data, and add lightweight API load tests.
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.
What will the state of AI be like in a year's time? Here are Mike Veerman's predictions of what major things will happen next in AI
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.