[stego-tech]

I’m not a developer, just an IT dinosaur, but one comment in the thread stuck with me:

> it has felt like a movement of “code first, think and ask questions later” took over the narrative during the past decade

That, I believe, is the real “hard reset” nobody is really talking about. Because the outcome is the same regardless of how AI goes:

* If AI is real, this progress continues, and magically half of my technical grievances are addressed, then thinking through the actual long-term problems, project planning, and technology architecture skills will explode in value overnight and the next millionaires will be Architects who can orchestrate and integrate complex systems with AI tooling…

OR

* This AI is just a fad, the bubble pops, and suddenly everyone who has “bandwagoned” into tech but not cultivated a growing skill set beyond coding problems will be forced out of a job. Those left behind will be the ones who kept their skills sharp and growing while everyone else drank the Kool-Aid, and no amount of community college programs or ITT Tech schemes will be able to create the amount of talent needed.

Just my two cents, and why I’ve been punching my way into architecture since COVID. I’m no dummy.

[jongjong]

I've been waiting for architecture skills to 'explode in value' for my entire 15+ years career. Basically the reverse happened thus far; architecture has been neglected and even the number of roles like 'Software Architect' and 'Solution Architect' have been on the decline.

I hope AI will force this shift to occur. Once the juniors stop thinking that they know everything, stop seeing themselves as coders and start seeing themselves as 'vibe coders'; they may be more inclined to rely on senior devs to evaluate 'their' code and to fill in the gaps.

Part of the issue before was that juniors who could churn out code at a rapid rate, didn't want to take advice from dinosaurs. I understand this very well because I was on the other side of the fence as a highly sought-after junior dev back in the day. I myself didn't see the value of senior devs back then.

Part of the issue is that it takes a long time/effort even to be a junior dev and so by the time junior devs can write any apps at all and they've read a couple of 'Software design patterns' books (sigh...), they think they're geniuses and don't need to take advice from anyone.

[geodel]

> Basically the reverse happened thus far; architecture has been neglected...

I see the same. My conclusion is a lot of people who'd be doing these marketing, analysts and many other low paying jobs where one needs to appear slick have now joined computer/IT due to hig pay in considerable numbers and to the point they hold positions of technical director etc.

At least in my experience I find this push for micro services, async, reactive, cloud, kubernetes, kafka which are part of "we are going state of the art" narrative is just to appear slick.

[stego-tech]

> At least in my experience I find this push for micro services, async, reactive, cloud, kubernetes, kafka which are part of "we are going state of the art" narrative is just to appear slick.

I can second this. If your stuff runs fine on a VM and provides more in value than it costs to support, then there’s no reason to move unless those technologies provide demonstrable/tangible value above and beyond their costs.

As for both of your comments, I’m also admittedly taking a swing for the fences here based on my read of the environment. A lot of metaphorical checks were written with the intent AI will pay them in full (or whatever the next fad is), but at some point the proverbial bill always comes due.