Engineering’s job has always been to deal with hard technical challenges and apply new technologies.
Writing code was never the point. Predictably creating specific outcomes was. Wrangling AI in a way that multiplies productivity is the new job.
I won’t lie, it kind of sucks to be young right now, learn about punch cards and assembly in school, and then graduate into a market that’s moved on to Fortran. Sorry, I meant high level languages and AI. To say otherwise might imply the industry has seen a similar shift in the past where engineers made the exact same complaints practically verbatim.
Regardless, the reality is that college teaches very little about 90% of real engineering work anyway, and we still need to hire smart people for this new type of work.
But we're a tiny baby startup, so things like "spin up a new product with 1 engineer and get to $1m in revenue on it" or "reduce our IaaS bill by 300k/yr" is a meaningful contribution for us.
We're also building new AI-enabled software that was not possible before.
The big breakout hits have been AI Infra, but that makes sense from a technological perspective, Cisco made a lot of money well before Google did, but Cisco is not where the money concentrated in the end.
We don't really know what the equivalent of Google as an application business will be in the AI era, but there's a pretty big chance it's not actual Google. But Google still has to do it's best to hold on.
Does not apply to everything though. E.G: I don’t care about AI support for my non work chats/email, since I’d rather not give it access.