Hacker News Reader

Comment by yawnxyz | Hacker News Reader

right, but this is akin to arguing why the table saw also does not do x/y/z — I don't know why we only complain about AI and how it does NOT do everything well yet.

Maybe it's expectations set by all the AI companies, idk, but this kind of mentality seems very particular to AI products and nothing else.

View on HN

I'm OK pondering the right use for the tool for as long as it'll take for the dust to settle. And I'm OK too trying some of it myself. What I resent is the pervasive request/pressure to use it everywhere right now, or 'be left out'.

My biggest gripe with the hype, as there's so much talk of craftmanship here, is: most programmers I've met hate doing code reviews and a good proportion prefer rewriting to reading and understanding other people's code. Now suddenly everyone is to be a prompter and astute reviewer of a flood of code they didn't write and now that you have the tool you should be faster faster faster or there's a problem with you.

well that's the issue. The table saw is a tool, we can very clearly agree it's good at cutting a giant plank of wood but horrible at screwing a bolt in. A carpenter can do both, but not a table saw. We never try to say the table saw IS the carpenter.

All this hype and especially the AGI talks want to treat the AI as an engineer itself. Even an assuredly senior engineer above is saying that it's better than them. So I think it's valid to ask "well can it do [thing a senior engineer does on the daily]" if we're suggesting that it can replace an engineer.

I'm not complaining about it, I said in my post that it's a huge time saver. It's here to stay, and that's pretty clear to see. It has mostly automated away the need for junior engineers, which just 5 years ago would have been a very unexpected outcome, but it's kind of the reality now.

All that being said:

There's a segment of the software eng population that has their heads in the sand about it and the argument basically boils down to "AI bad". Those people are in trouble because they are also the people who insist on a whole committee meeting and trail of design documents to change the color of a button on a website that sells shoes. Most of their actual hard skills are pretty easy to outsource to an AI.

There's also a techbro segment of the population, who are selling snake oil about AGI being imminent, so fire your whole team and hire me in order to outsource your entire product to an army of AI agents. Their thoughts basically boil down to "I'm a grifter, and I smell money". Nevermind the fact that the outcome of such a program would be a smoldering tire fire, they'll be onto the next grift by then.

As with literally everything, there are loud, crazy people on either side and the truth is in the middle somewhere.

Junior engineers will be fine; OpenAI is actually choosing to hire juniors now because they just learned all their theory and structure, and are way more willing to push the LLMs to see what they can do.

Bad code is bad code. There’s been bad code since day one; the question is how fast are you willing to fail, learn, fail again, learn more, and keep going.

LLMs make failing fast nearly effortless, and THAT is power that I think young people really take to.

Failing is part of the learning process if you learn from it. Otherwise it's just failing.

Reply on news.ycombinator.com