Most active commenters

    ←back to thread

    342 points tareqak | 12 comments | | HN request time: 1.04s | source | bottom
    Show context
    johncole ◴[] No.44469537[source]
    I think we will see this lead to a boost in software developer employment.
    replies(5): >>44469626 #>>44469700 #>>44469839 #>>44469938 #>>44469999 #
    mlinhares ◴[] No.44469839[source]
    I doubt it, the narrative is that software engineering is dead and everything will be replaced by AI, so that salaries can continue to be depressed. Just like the original passing didn't really cause much trouble in the general market this repeal will mostly just produce more shareholder value.
    replies(3): >>44469868 #>>44470043 #>>44470207 #
    1. seattle_spring ◴[] No.44470043[source]
    Anyone who knows anything about software and has used AI for more than 24 hours knows that AI won't be "replacing" software engineering anytime soon.
    replies(2): >>44470070 #>>44470456 #
    2. ldjkfkdsjnv ◴[] No.44470070[source]
    ive been coding 5+ hours a day almost every day for 15 years. i think ai will replace 70% of SWE in the near future. not employement, but 70% of the current work done by engineers
    replies(4): >>44470205 #>>44470358 #>>44470470 #>>44471248 #
    3. hightrix ◴[] No.44470205[source]
    Agreed. I see AI as a major tool upgrade in the same way the IDE was an upgrade from text editors. It will quickly replace the need to do trivial things and greatly reduce the time needed to do complex things.
    4. jnfno ◴[] No.44470358[source]
    I’ve been coding 5+ a day since the late 80s

    And I agree. Because ultimately we don’t need that much code in the first place. We need robust data sets.

    AI models will enable the data driven machine state dream. Chips that self improve models will boot strap from them and rely on humans to iteratively improve updates.

    Coding like it’s 1970 in the 2020s and beyond is not that high tech.

    5. akmarinov ◴[] No.44470456[source]
    Hard disagree, I’ve been agentic coding the past couple of months and have written maybe 100 lines doing this for a living.

    The rest is coming up with SDDs and reviewing AI’s code.

    I can easily see most devs, doctors and lawyers automated away in the next couple of years.

    replies(2): >>44470488 #>>44470764 #
    6. zeroonetwothree ◴[] No.44470470[source]
    I don’t even spend 70% of my time coding. I suspect that’s common and looking at data it’s more like 25% on average. So even if it replaces 100% of coding (unlikely) that’s the extent of the gain.
    replies(2): >>44471537 #>>44472468 #
    7. throwawaysleep ◴[] No.44470488[source]
    Very much agree.

    I am overemployed with 3 dev jobs at once. AI is writing virtually all my code and letting me nap all day. Eventually that will end once people see the power of them.

    8. coffeebeqn ◴[] No.44470764[source]
    Either we have wildly different difficulty levels at our jobs or this is bs. I tried the agents (I get access to basically all state of the art from my company) and they still have all the same issues of agents from a year back. Each step gets more chaotic and the end result is always that I end up reverting the over complicated mess it made and writing it myself. One-offs with lots of context still sometimes work.

    Even a perfect eval loop like failing tests end up 80% of the time with them creating something way too complicated since they solve one visible but not root issue at a time and build on top of that hacky foundation until again I end up reverting it all

    replies(1): >>44471300 #
    9. AnthonyMouse ◴[] No.44471248[source]
    At which point you're potentially looking at Jevon's Paradox.

    Software developers do X and Y. AI thing can now do X, so it's used for that, and it's cheaper, so the number of projects increase because you get more demand at a lower price. Those projects each need someone to do Y.

    10. akmarinov ◴[] No.44471300{3}[source]
    Yeah - that’s the hard part now - dialing things down to eliminate the divergent paths the AI can take to implement what you want.

    You can tell it “implement feature X” and it’ll go and do whatever’s easiest for it, often something dumb, that’s when people usually think “it’s dumb, won’t replace devs” and give up. Or you can nail down your requirements by talking to it and describing what you’re looking for, often it comes back with things you hadn’t considered or ways of doing things you didn’t know. Then just tell it “implement this SDD” and watch it one shot it in an hour or so.

    There’s also pain points - some languages like Swift have changed so often and there’s little open source code to train on out there, so it’s on the worse side if you do iOS development.

    It’s a new skill that needs working at, but in the end your output is significantly increased.

    11. distances ◴[] No.44471537{3}[source]
    Agreed, seems it's a great day if I get close to 50% of coding time. The rest is various meetings, communication, and code review.

    And even with reviews you can currently plausibly automate only the code correctness check part, the juicy part of reviews is always manual testing of the change and doing the logical reasoning if the change is doing a meaningful thing. And no, the ticket with the spec is not a reliable source of this info for an LLM as it's always just a partial understanding of the concept.

    12. kasey_junk ◴[] No.44472468{3}[source]
    Some of my biggest productivity gains with llms come from areas that aren’t coding. Research, summation, communication and operational issues have all seen pretty dramatic improvements for me when adding llms.

    I don’t think ai will replace the career of software development but I do think the tools we will be using to to it will be dramatically different.