Engineering

Newsletter

From Andreas' Desk

A bi-weekly letter from our CEO Andreas Creten for SaaS leaders and CTOs: what we see in audits, AI engineering and the companies we work with.

You're in — check your inbox to confirm.

From our SaaS audits

What we find inside SaaS companies

Patterns from the technical due diligences we run for investors and boards.

See the audit findings

Investor Insights #6 - Andreas’ new book: The Economics of Software Engineering

The full-stack enigma

Early-stage startups want full-stack unicorns who can do it all on a tight budget, but asking one dev to wear every hat is less strategic hiring and more duct-taping a rocket and hoping for the best.

On the imminent retirement of the keyboard - the future of software engineering

By 2030, nobody will write code anymore and here is why. The difference between agent-powered engineers and those who handcraft code is huge. Here's our prediction on software engineering.

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.

The CTO's guide to AI adoption strategy

AI adoption fails when treated as a tool rollout. This guide covers the decision framework, team dynamics, economics, and mistakes from 190+ technical audits.

A guide to vibe coding vs AI-assisted development

Vibe coding or AI-assisted development? The choice isn't binary, but getting it wrong at the wrong stage will cost you. This piece breaks down when to embrace speed over architecture, when to take back control, and why the best teams don't pick sides.

How to introduce AI coding agents into your engineering team

AI coding agents draft code, write tests, and open pull requests autonomously. This guide covers the tool landscape, readiness signals, a phased rollout plan, and the team dynamics that make or break adoption.

AI code review tools: what works, what doesn't, and how to set it up

AI code review catches what humans miss and misses what humans catch. This guide compares the tools, shows what each catches, and walks through setup without replacing human judgment.

Communicate or be micromanaged - the engineering edition

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.

The value of code review

Code reviews improve more than code quality. Done well, they shape better problem-solving, expose edge cases, and spread knowledge across teams. Learn how small, focused reviews and AI support help teams ship faster with confidence.

Getting started with performance testing

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.

How to pragmatically leverage AI as a startup

If you believe what you see on LinkedIn, startups don't need employees anymore, real founders just have agents building their companies. You write a prompt, fire off the agent, and wait for customers. In reality, you get a vague workflow that produces a mediocre demo at best.

Cloudy with a chance of function calls

In the first of a series exploring infrastructure fundamentals, Brenden addresses the most frequently asked questions about what's really happening under the hood with complex pipelines and AI/data systems, bringing the cloud to life.

Analyse your tables for better performance

I recently encountered a issue with MySQL query performance. A particular query would perform very badly in production, but perform very well in the testing environments.

No designer? No problem with v0

For small teams without a designer, v0 is a game-changer. The cost justifies itself by letting you explore and validate ideas in minutes rather than days.

Subscribe