Simon Schrottner

@aepfli.bsky.social

Father, CouchSurfer, JUnit-Pioneer Maintainer, OpenFeature Maintainer

The agent runs the fastest #loop anyone has ever had: output, correction, output again, until the code matches the spec. What it can't correct is the spec. Questioning the frame instead of the output is a different loop, an older and slower one, and it still needs the room. #LeftOfTheLoop #AI

Teams have always known that upfront alignment produces better estimates, and that's not a new idea. What's new is that #AI makes the alternative, skipping the alignment, running the agent, seeing what happens, feel so productive in the moment that the incentive to do the upfront work disappears.

hot take: most companies are just giving devs AI tools and calling it innovation 🙃 wrote about what I think actually needs to change — spoiler: it's not the tooling, it's the process and yes, I am leaning on XP terminology. no regrets ;) schrottner.at/2026/06/18/T... #softwaredevelopment #ai

The Wrong End of the Problem

Every company wants AI in their development process right now. That part is clear. What’s less clear is where they’re putting it.

schrottner.at

We've been putting ourselves in the middle of the software delivery lifecycle. By design. 🤔 What if the job is writing fitness functions instead? 🤔 Not reviewing pull requests, but defining what survival looks like.

The worst part of being laid off so far, was the uncertainty, what's next, when, how, etc. Somehow this is a new level of discomfort for me. Externally induced, but I already feel like I am learning something. And to be honest - the community (everywhere), is amazingly supportive. Thank you all!

What started as “let’s add some OpenTelemetry to a Python game” for my talk… …turned into a microservice refactor, clear service boundaries, and CI/CD everywhere. AI-assisted dev speed was wild. Dashboards, traces & metrics weren’t just visibility - they fueled the refactoring. Massive learnings 🤯