[tripledry]

Sure, IF the performance + economics is there. But that doesn't sound like an enjoyable profession to me.

I enjoy the plan, think, code cycle - it's just fun.

My brain has problems with not understanding how the thing I'm delivering works, maybe I'll get used to it.

[weatherlite]

To me it's more of a mixed bag. On the one hand - disheartening to see how the knowledge base and skills I've worked more than a decade to develop became of little value (not worthless, but not as valuable as before). Also - yeah, the speed of delivery that is going to be expected of devs will make it so we will not be able to hold all the pieces in our heads and rely on A.I (when things break it will suck, hopefully A.I will be able to get us out of the jam). This is also not enjoyable to me.

On the other hand : way less time spent on being stuck on yarn/pip dependency issues, docker , obscure bugs , annoying css bugs etc etc. You can really focus on the task at hand and not spend hours/days trying to figure out something silly.