Live data from Hacker News

AI’s impact on engineering jobs may be different than expected

semiengineering.com

31–40 of 231 posts

Re: AI’s impact on engineering jobs may be different than expected

#32

Senior dev here 15 years experience just turned 50 have family blah blah. I've been contracting for the last two years. The org is just starting to use Claude. I've been delegating - well copy pasting - into chatgpt which has to be the laziest way to leverage AI. I've been so successful (meaning haven't had to do anything really except argue with chatgpt when it goes off on some tangent) with this approach that I can…

> I swear when this contract is over I'm opening a mobile food cart.

This is the way. I think I'd like to be a barista or deliver the mail once all the jobs are gone.

Re: AI’s impact on engineering jobs may be different than expected

#33
"Most people who drive cars now couldn’t find the radiator cap if they were paid to, and that’s fine."

That's not fine IMO. That is a basic bit of knowledge about a car and if you don't know where the radiator cap is you will eventually have to pay through the nose to someone who does know (and possibly be stranded somewhere). Knowing how to check and fill coolant isn't like knowing how to rebuild a transmission. It's very simple and anyone can understand it in 5 minutes if they only have the curiosity.

Re: AI’s impact on engineering jobs may be different than expected

#34
"in the 1920s and 1930s, to be able to drive a car you needed to understand things like spark advance, and you needed to know how to be able to refill the radiator halfway through your trip"

A car still feels weirdly grounded in reality though, and the abstractions needed to understand it aren't too removed from nature (metal gets mined from rocks, forged into engine, engine blows up gasoline, radiator cools engine).

The idea that as tech evolves humans just keep riding on top of more and more advanced abstractions starts to feel gross at a certain point. That point is some of this AI stuff for me. In the same way that driving and working on an old car feels kind of pure, but driving the newest auto pilot computer screen car where you have never even popped the hood feels gross.

Re: AI’s impact on engineering jobs may be different than expected

#35
post #9

The main thing to understand about the impact of AI tools: Somehow the more senior you are [in the field of use], the better results you get. You can run faster and get more done! If you're good, you get great results faster. If you're bad, you get bad results faster. You still gotta understand what you're doing. GeLLMan Amnesia is real.

> Somehow the more senior you are [in the field of use], the better results you get.

It's a K-type curve. People that know things will benefit greatly. Everyone else will probably get worse. I am especially worried about all young minds that are probably going to have significant gaps in their ability to learn and reason based on how much exposure they've had with AI to solve the problems for them.

Re: AI’s impact on engineering jobs may be different than expected

#36

Senior dev here 15 years experience just turned 50 have family blah blah. I've been contracting for the last two years. The org is just starting to use Claude. I've been delegating - well copy pasting - into chatgpt which has to be the laziest way to leverage AI. I've been so successful (meaning haven't had to do anything really except argue with chatgpt when it goes off on some tangent) with this approach that I can…

Same, except I am over 60 and when I think of opening a mobile food cart it is sort of a Blade Runner vibe, staffed by a robot ramen chef that grumbles at customers and always says something back to you in some cyber slang that you don’t understand.

Re: AI’s impact on engineering jobs may be different than expected

#37

Its pretty clear that any white collar work where the outputs can be verified and tested in a reinforcement learning environment, will be automated

Ironically I feel like our QA team is busier than ever since most e2e user-ish tests require coordinating tools that is just beyond current LLM capabilities. We are pumping out features faster that require more QA to verify.

Re: AI’s impact on engineering jobs may be different than expected

#38

Senior dev here 15 years experience just turned 50 have family blah blah. I've been contracting for the last two years. The org is just starting to use Claude. I've been delegating - well copy pasting - into chatgpt which has to be the laziest way to leverage AI. I've been so successful (meaning haven't had to do anything really except argue with chatgpt when it goes off on some tangent) with this approach that I can…

I have read this same comment so many times in various forms. I know many of them are shill accounts/bots, but many are real. I think there are a few things at play that make people feel this way. Even if you're in a CRUD shop with low standards for reliability/scale/performance/efficiency, a person who isn't an experienced engineer could not make the LLM do your job. LLMs have a perfect combination of traits that cause people to overestimate their utility. The biggest one I think is that their utility is super front-loaded.

If a task before would take you ten hours to think through the thing, translate that into an implementation approach, implement it, and test it, and at the end of the ten hours you're 100% there and you've got a good implementation which you understand and can explain to colleagues in detail later if needed. Your code was written by a human expert with intention, and you reviewed it as you wrote it and as you planned the work out.

With an LLM, you spend the same amount of time figuring out what you're going to do, plus more time writing detailed prompts and making the requisite files and context available for the LLM, then you press a button and tada, five minutes later you have a whole bunch of code. And it sorta seems to work. This gives you a big burst of dopamine due to the randomness of the result. So now, with your dopamine levels high and your work seemingly basically done, your brain registers that work as having been done in those five minutes.

But you now (if you're doing work people are willing to pay you for), you probably have to actually verify that it didn't break things or cause huge security holes, and clean up the redundant code and other exceedingly verbose garbage it generated. This is not the same process as verifying your own code. First, LLM output is meant to look as correct as possible, and it will do some REALLY incorrect things that no sane person would do that are not easy to spot in the same way you'd spot them if it were human-written. You also don't really know what all of this shit is - it almost always has a ton of redundant code, or just exceedingly verbose nonsense that ends up being technical debt and more tokens in the context for the next session. So now you have to carefully review it. You have to test things you wouldn't have had to test, with much more care, and you have to look for things that are hard to spot, like redundant code or regressions with other features it shouldn't have touched. And you have to actually make sure it did what you told it to, because sometimes it says it did, and it just didn't. This is a whole process. You're far from done here, and this (to me at least) can only be done by a professional. It's not hard - it's tedious and boring, but it does require your learned expertise.

Re: AI’s impact on engineering jobs may be different than expected

#39

"Most people who drive cars now couldn’t find the radiator cap if they were paid to, and that’s fine." That's not fine IMO. That is a basic bit of knowledge about a car and if you don't know where the radiator cap is you will eventually have to pay through the nose to someone who does know (and possibly be stranded somewhere). Knowing how to check and fill coolant isn't like knowing how to rebuild a transmission. It'…

I have never cared for decades and now my car doesn't even have a radiator. Seems to have worked out well for me.

Re: AI’s impact on engineering jobs may be different than expected

#40

"Most people who drive cars now couldn’t find the radiator cap if they were paid to, and that’s fine." That's not fine IMO. That is a basic bit of knowledge about a car and if you don't know where the radiator cap is you will eventually have to pay through the nose to someone who does know (and possibly be stranded somewhere). Knowing how to check and fill coolant isn't like knowing how to rebuild a transmission. It'…

Ironically, many cars don't have radiator caps, only reservoirs.

Modern cars, for the most part, do not leak coolant unless there's a problem. They operate a high pressure. Most people, for their own safety, should not pop the hood of a car.

Post reply on HN