Blog

Thoughts on AI-native Software Engineering, productivity, and building great products.

I don't trust any AI agent

STDD Loop: Spec first, OK Point (human and/or agent), tests first, Audit Trail, Guardrails – comic

I don't trust any AI agent. And yet one just built an entire feature set, almost without my hands on the keyboard. Not because I trust it, but because every step leaves an audit trail.

20X – Why I'm So Insanely Productive with AI

20X – comic: Mischa on the bicycle, Technology Leap × Learning Leap × Acceleration

For fifteen years I didn't build software myself. When I came back, a job that used to need a whole ops team was down to one click. Being 20X more productive isn't magic, it's a multiplication of three forces: Technology Leap, Learning Leap, Acceleration.

I am addicted

I am addicted – comic

Hi, my name is Mischa. And I'm addicted to AI-native software engineering. How to live with that addiction, where it gets dangerous, and how responsibility takes the place of the rush.

Agile is too rigid for AI-native

Agile was my second professional love – comic

Agile was my second professional love. Today I say goodbye. For over ten years I lived, taught, and scaled Agile. A year ago, when I typed my first prompt, it hit me pretty quickly why Agile no longer fits AI-native.

AI ate Agile for Breakfast

AI eats Agile for Breakfast – talk comic

A decade after stepping back from the Lean Agile Scrum (LAS) community, I wanted to speak up again with a bold thesis: AI eats Agile for Breakfast. The conference was cancelled. Three weeks later I'm giving the opening keynote somewhere else – plus a workshop. Even the cancellation proved the thesis.

The right entry into AI-native Software Engineering

Build one real system, then decide how to scale – the Beacon reference system

Whether the transition to AI-native Software Engineering is successful depends on how developers and management deal with the change and what conclusions they draw for roles, structures, and processes. A small, real-world AI beacon provides the necessary foundation.

Why introducing AI fails

Why simple AI introductions fail – the rollout gap

The problem is the entry point: instead of building, organizations explain; instead of anchoring responsibility, they prepare. AI introductions start where they cannot have any effect – on paper. AI only unfolds its impact where software is actually built.

AI makes coding easier. Software engineering gets harder.

AI makes coding easier – software engineering gets harder

AI lowers the barrier to writing code – yet building production software reveals the opposite: software engineering gets harder. Leadership becomes the real work, every prompt iteration a decision. Being able to code well is no longer enough.

Stagnation doesn’t come from doubt, but from responsibility

Stagnation from responsibility – the safer way into AI-native software engineering

AI has arrived in software engineering. And yet, surprisingly little is happening in many organizations. Many leaders hesitate, not out of skepticism, but out of responsibility.