Navigating the EU AI Act: Harsh Reality or Healthy Discipline for Developers?
Sunday Reflection — 2026-11-08
On Tuesday I watched a senior developer slam his laptop lid and mutter about “paperwork for robots”. He’s not lazy. He’s tired. The latest round of EU AI Act compliance landed on his desk—risk logs, update forms, documentation for the documentation. We spent forty minutes arguing about what counts as a “high-risk system” before starting a single line of code. That’s a new ritual, these days.
mermaid flowchart TD A[New AI Feature Idea] --> B[Check EU AI Act Risk Class] B -->|Minimal/None| C[Proceed with Coding] B -->|High-risk| D[Draft Docs & Risk Log] D --> E[Review with Team] E --> F[Send for Compliance Approval] F --> G[Client Feedback] G -->|Happy| C G -->|More Changes| D
Some say this is overdue—finally treating AI like something that can break things or hurt people, not just automate away the dull bits. But it’s a far cry from shipping early or “move fast and break things”. Last week in the classroom, I had to spend half a lesson walking career-changers through why every decision now needs a paper trail. One of the students—ex-baker from Neukölln, sharp mind, didn’t mince his words—asked, “Will any of this stop a bad actor, or just slow down good ones?” I didn’t have a clean answer. Some German teams I’ve worked with thrive on these rules. There’s a pride in getting every requirement checked off. British pragmatism, on the other hand, would rather fix problems as they come and skip the theoretical disasters. Both models hit their limits when the paperwork stacks higher than the code.
There are upsides. I once lost two weeks chasing a production bug that vanished because nobody wrote down which dataset version ran where. That wouldn’t happen under these new rules. But the price is real—a visible dip in team morale, clients twitchier about every pause for approvals, and students who now need just as much training in regulation as in algorithms. The discipline helps. The bureaucracy grinds.
One thing strikes me most: compliance isn’t just a technical problem. It’s a change in how teams talk, plan, and trust. You can engineer for security. Culture’s harder. But that’s the test the EU’s set us. Will tighter rules make us safer, or just slower? Worth pondering, if you’re writing software—or teaching it—this winter.