But how many "architecture decisions" do you really have to make when it comes to any proper project? Also "making decisions on the user interface" is literally what frontend engineers have done for years (so you're still working as an engineer while you claim to be a "manager"). If you are in programming and programming is not your strong suite, the moral thing to do is either get better at programming or seek an actual manager job where it makes sense to use the "part of the brain" you are good at. Why do you need to pretend that being a good manager = being a good programmer? Why do you not care about being a good programmer and just the output of waht the agents are doing? You're purely thinking of it from a business pov and optimizing time but you're missing the individual programmer who actually sees value in programming and wants to get better.