Not sure if I'll close the loop yet..
Do any of the more experienced coders ever feel like closing the loop in vibecoding is a bit too much control to let go off? I'm not sure if I can categorize myself as an experienced coder. I'm been mainly self-taught and been doing it for almost a decade now, so I have strong opinions about what I consider best practices. (I actually love refactoring, because it feels like order is once again restored in the codebase).
However, with AI becoming so good at so many parts of the product development, I'm starting to feel like a project manager, or god forbid, scrum master... On the one hand, it's nice that I get to spend most of my time thinking about the problems themselves rather than the implementation of the solution. But on the other hand, I think my coding style is a bit like trying to find a way out of a dark room by running into the wall repeatedly as opposed to planning a way out. And I kind of missing running into the wall to be honest. Now, I'm enviously looking at AI hitting the wall.
I kind of managed to clone myself in my AI agents, so my strong opinions are often enforced, which works quite well actually, but I'm not sure if I will close the rest of the loop yet.
How do others think about this?
Replies
I feel this deeply. We’ve spent a decade finding 'order' through manual refactoring and hitting those walls ourselves. It’s hard to trade that satisfying 'a-ha!' moment for the efficiency of an agent. While things are changing fast, maybe the new 'best practice' isn't just the code itself, but how we encode our strong opinions into the agents we build. We aren't just Scrum Masters; we're the Architects of the loop.