September 19, 2026
Some thoughts on AI, mainly the coding agent side of things
Been thinking a lot lately and need to write things down.
Agentic coding, in essence
I have been using code agents for all my side projects for roughly the past 18 months and it has completely changed the way I think about programming. Granted, my setup is elaborate and far from just running a prompt in something like Claude or ChatGPT online. And it evolved at incredible speed, roughly 6 completely different approaches, with some side quests. Agentic coding is NOT getting a subscription, downloading a CLI tool and off you go. The output will not be what you want it to be. I tuned my entire workflow to accommodate agentic coding, from eslint rules to symbol mappers to wiki-like knowledge bases with pitfalls and patterns.
I have to admit, I always liked programming for the sake of fleshing out a vision or a requirement. To me, it is a tool, a way to manifest my own or a clients requirements in a software tool. I never liked programming for the sake of the programming itself, needlessly complex toolchains or other distractions. Frontend development especially is and has been a mess for as long as I can remember, that doesn’t help.. And there have been evangelists for one or the other way of doing something for as long as programming has existed. So nothing has changed and probably never will on that front.
Right now I notice a lot of collective amnesia. I have to chuckle when I read that people blame LLM output for being wrong or introducing bugs. Like nobody ever introduced bugs? Like every piece of software written in the last 45 years is perfect? How threatened do we need to feel to completely block that out? The iterative process remains. We stand at the beginning of a new era. All previous attempts that tried to abstract the act of coding away from feature development pale in comparison to what is currently going on. And as a single person working on something, I can have 3 agents develop individual features or let them orchestrate to work on a fullstack feature. It is so much more efficient. Even if I have to nudge every single task to get it right to where I want it, it is still more efficient, because not only can I work on 3 tracks at the same time, but I also have the capacity on top of that to think about the big picture of whatever I want to achieve, without getting lost in technical details.
I am not sure how to express this, but I think either you really try to get used to the workflow - find that flow, work with it and not against it, find your individual way for your individual requirements - or agentic coding is not your cup of tea and you go on doing it the way you are used to. To reach flow state, problem-solving remains the most prominent trigger for me. And that is still my job to a large extent. It just shifts a little bit.
I do not see anything wrong with either agentic coding or sticking to the path. If you are the kind of programmer who can reminisce for hours on the beauty of algorithms, I am the last person who wants to take that away from you. I completely get it. I feel the same when I see my ideas coming together.
- Yes, there is always a way to not do it, with every tool. That includes LLMs for coding.
- Yes, your architecture will suck after running 24 agents for a week without a single review.
- Yes, vague instructions don’t just confuse juniors or your coworkers, they also confuse agents.


























