5 ms·
"Jobs are going to be lost unless there's somehow a demand for more applications." That's why I'm not worried. There is already SO MUCH more demand for code th
by simonw 2y ago
"Jobs are going to be lost unless there's somehow a demand for more applications."
That's why I'm not worried. There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next.
I think LLM assistance makes programmers significantly more productive, which makes us MORE valuable because we can deliver more business value in the same amount of time.
Companies that would never have considered building custom software because they'd need a team of 6 working for 12 months may now hire developers if they only need 2 working for 3 months to get something useful.
- sitkack 2y agoWe have already entered a new paradigm of software development, where small teams build software for themselves to solve their own problems rather than making software to sell to people. I think selling software will get harder in the future unless it comes with special affordances.
- LeFantome 2y agoI think some of the CEOs have it right on this one. What is going to get harder is selling “applications” that are really just user friendly ways of getting data in and out of databases. Honestly, most enterprise software is just this. AI agents will do the same job. What will still matter is software that constrains what kind of data ends up in the database and ensures that data means what it is supposed to. That software will be created by local teams that know the business and the data. They will use AI to write the software and test it. Will those teams be “developers”? It is probably semantics or a matter of degree. Half the people writing advanced Excel spreadsheets today should probably be considered developers really.
- butlike 2y agoMaybe, but it's the same argument trickling down. You'll need the CRUD-apps because you hired Cindy to press the button, and if shit goes pear-shaped, you can point to Cindy in the post-mortem. If it's some AI agent pressing the button to egress data from the database, and there's an anomaly, then it's a systemic failure at a macro level at that company, which is harder to write a press release about.
- sitkack 2y agoMany applications can and should be replaced by a prompt and a database. This is the nature of increased expressive and computational power. So many whip manufacturers are about to go out of business, especially those offering whips-as-a-service.
- bee_rider 2y agoMostly agree, even without a database-centered worldview. Programming languages are languages to tell the computer what to do. In the beginning, people wrote in machine code. Then, high level languages like C and FORTRAN were invented. Since then we’ve been iterating on the high level language idea. These LLM based tools seem to be a more abstract way of telling the computer what to do. And they really might, if they work out, be a jump similar to the low/high level split. Maybe in the future we’ll talk about low-level, high-level, and natural programming languages. The only awkwardness will be saying “I have to drop down to a high level language to really understand what the computer is doing.” But anyway, there were programmers on either side of that first split (way more after), if there’s another one I suspect there will still be programmers after.
- cess11 2y agoNo, enterprise software is typically also risk management and compliance, domains where rules rule. Someone needs to sign off on the software being up to spec and taking responsibility for failures, that's something any submissive LLM is willing to do but can't.
- kakapo1988 2y agoAt some point, I wonder if there will be advantageous for AI to just drop down directly into machine code, without any intermediate expression in higher-level languages. Greater efficiency? Obviously, source allows human tuning, auditing, and so on. But taken at the limit, those aspects may eventually no longer be necessary. Just a riff here, as the thought just occurred.
- sureglymop 2y agoIn the past I've had a similar thought, what if the scheduler used by the kernel was an AI? better yet, if it is able to learn your usage patterns and schedule accordingly.
- __MatrixMan__ 2y ago...which is a good thing. Software made by the people using it to better meet their specific needs is typically far better than software made to be a product, which also has to meet a bunch of extra requirements that the user doesn't care about.
- jeswin 2y ago> That's why I'm not worried. There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. I worry about junior developers. It will be a while before vocational programming courses retool to teach this new way of writing code, and these are going to be testing times for so many of them. If you ask me why this will take time, my argument is that effectively wielding an LLM for coding requires broad knowledge. For example, if you're writing web apps, you need to be able to spot say security issues. And various other best practices, depending on what you're making. It's a difficult problem to solve, requiring new sets of books, courses etc.
- simonw 2y agoYeah, it's going to suck for junior developers for a while. The ones who are self-starters will do fine - they'll figure out how to accelerate their way up the learning curve using these new tools. People who prefer classroom-learning / guided education are going to be at a disadvantage for a few years while the education space retools for this new world.
- antonislav 2y agoI think, seeing recordings of people using LLMs to accomplish non-trivial tasks would go a long way. I’d love to watch, e.g. you Simon, using these tools. I assume there are so many little tricks you figured out over time that together make a big difference. Things that come to mind: - how to quickly validate the output? - what tooling to use for iterating back and forth with the LLM? (just a chat?) - how to steer the LLM towards a certain kind of solutions? - what is the right context to provide to the LLM? How do it technically?
- plandis 2y agoI believe Simon has full transcripts for some of the projects he’s had LLMs generate the code for. You can see how he steers the LLM for what is desired and how it is course corrected.
- SecretDreams 2y agoThe big fear shouldn't be on loss of jobs, it should be the inevitable attack on wages. Wage will track inversely to proximity as a commodity status. Even the discussion around AI partially replacing coders is a direction towards commoditization.
- Espressosaurus 2y agoIt's the same thing. If there are more workers than jobs, wages go down. If there are more jobs than workers, wages go up. We saw it crystal clear between the boom years, the trough, and the current recovery.
- UncleOxidant 2y ago> That's why I'm not worried. There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. And yet many companies aren't hiring developers right now - folks in the C suite are thinking AI is going to be eliminating their need to hire engineers. Also "demand" doesn't necessarily mean that there's money available to develop this code. And remember that when code is created it needs to be maintained and there are costs for doing that as well.
- simonw 2y agoI continue to suspect that the hiring problems are mainly due to massive over-hiring during Covid, followed by layoffs that flooded the market with skilled developers looking for work. I'd love to see numbers around the "execs don't think they need engineers because of AI" factor. I've heard a few anecdotal examples of that but it's hard to tell if it's a real trend or just something that catches headlines.
- menaerus 2y agoMassive overhiring or not, it's the fact that many (skilled) engineers can't find a job. Many companies were shut off during the past few years and market became oversaturated over the night. Whether AI will help to correct the market creating more demand we will see but I wouldn't hold my breath. Many domain specific skills became a commodity.
- nwienert 2y agoWhere's the fact coming from, as in it's higher than before? I seem to be getting more than ever recruiting emails, and have felt out interviewing at a few places which we're very eager to find staff level talent.
- menaerus 2y agoPersonal experience and also from many people I know around. Previously I would receive a request for an interview every two days or so. Lately, perhaps once a month, if at all. Foundational skills that I have were always scarce on the market so that makes me believe that the demand for them is now much much lower. Another data point is that there's been ~10 companies that I have been following and all of them have been shut down in the past year or so. And the general feeling you get from the number of HN posts from people complaining about not being able to find jobs. This certainly hasn't been like that before.
- Scipio_Afri 2y ago100% agree with this take. People are spouting economic fallacies, and it’s in part cause CEOs don't want the stock prices to fall too fast. Eventually people will widely realize this and by then the economic payoffs are still immense.
- aomix 2y agoI’m more bearish about LLMs but even in the extreme optimist case this is why I’m not that concerned. Every project I’m on is triaged as the one that needs the most help right now. A world when dozen projects don’t need to be left on the cutting room floor so one can live is a very exciting place.
- deadbabe 2y agoToo much productivity can be a bad thing. If you’re infinitely productive, then the solution to every problem is to just keep producing stuff, instead of learning to say no. This means a lot of companies will overbuild, and then drown in maintenance problems and fail catastrophically when they can’t keep up.
- littlestymaar 2y agoI couldn't agree more. And this kind of fear mongering is particularly irritating when you see that our industry already faced a similar productivity shock less than twenty years ago: before open source went mainstream github and library hubs like npm we used to code the same things over and over again, most of the time in a half-backed fashion because nobody had time for polishing stuff that was needed but only tangentially related to the code business. Then came the open-source tsunami, and suddenly there was a high quality library for solving your particular problem and the productivity gain was insane. Fast forward a few years, does it look like this productivity gains took any of our jobs? Quite the opposite actually, there has never been as many developers as today. (Don't get me wrong, this is massively changing how we work, like the previous revolution did, and how job is never going to be the same again)
- aibot923 2y agoIt's interesting. Maybe I'm in the bigtech bubble, but to me it looks like there isn't enough work for everyone already. Good projects are few and far between. Most of our effort is keeping the lights on for the stuff built over the last 15-20 years. We're really out of big product ideas.
- agsqwe 2y agoThis is very similar to my experience as a software development agency to enterprise customers. Out of big product ideas.
- nkassis 2y agoYes a capacity increase from the developer side is great but it's supply side and we need to figure out how to accelerate transforming needs into demand. This is what I foresee developers turning into (at least some capable of this). Articulating logical solutions to be built to problems and evaluating results from what's generated to ensure it meets the needs. Aka Devs can move up the chain into what was traditionally product roles to increase development of new projects. This is using the time they have regain from more menial tasks being automated away.
- AlwaysRock 2y agoGood projects !== work There is a lot of work. Plenty of it just isnt super fun or interesting.
- __MatrixMan__ 2y agoThat's because software is hard to make, and most projects don't make it far enough to prove themselves useful--despite them having the potential to be useful. If software gets easier, a whole new cohort of projects will start surviving past their larval stage. These might not be big products, but who wants big products anyway? You always have to bend over backwards to trick them into doing what you want. You should see the crazy stuff my partner does to make google docs fit her use case... Let's have an era of small products made by people who are close to the problems being solved.
- AlwaysRock 2y agoYup. People who know how to use it, and who work on tasks where LLM code is generally functional, are getting more done in less time. I don't trust companies to translate that to, "We can do more now" rather than, "We can do more with less people now" though.
- ksec 2y ago>There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. We really are in AI moment of iPhone. I never thought I would witness something bigger than the impact of Smartphone. There are insane amount of value that we could extract out. Likely in tens of trillions from big to small business. We keep asking how Low Code or No Code "tools" could achieve custom apps. Turns out we are here via a different route. >custom software because they'd need a team of 6 working for 12 months may now hire developers if they only need 2 working for 3 months to get something useful. I am wondering if it be more like 2 working for 1 month?
- fragmede 2y agoless. how long would it take to build Twitter if you throw out all the difficult backend scaling problems and assume a supabase db was enough?
- paulryanrogers 2y agoDev effort isn't always the bottleneck. It's often stakeholders ironing out the ambiguities, conflicting requirements, QA, ops, troubleshooting, etc. Maybe devs will be replaced with QA, or become glorified QA themselves.
- gamblor956 2y agoShow me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. Most companies don't have a milelong backlog of coding projects. That's a uniquely tech industry-specific issue, and a lot of it is driven by the tech industry's obsessive compulsion to perpetually reinvent wheels. Companies that would never have considered building custom software because they'd need a team of 6 working for 12 months may now hire developers if they only need 2 working for 3 months to get something useful. No, because most companies that can afford custom software want reliable software. Downtime is money. Getting unreliable custom software means that the next time around they'll just adapt their business processes to software that's already available on the market.
- rybosworld 2y ago> There is already SO MUCH more demand for code than we're able to keep up with. Show me a company that doesn't have a backlog a mile long where most of the internal conversations are about how to prioritize what to build next. This is viewing things too narrowly I think. Why do we even need most of our current software tools aside from allowing people to execute a specific task? AI won't need VSCode. If AI can short circuit the need for most, if not nearly all enterprise software, then I wouldn't expect software demand to increase. Demand for intelligent systems will certainly increase. And I think many people are hopeful that you'll still need humans to manage them but I think that hope is misplaced. These things are already approaching human level intellect, if not exceeding it, in most domains. Viewed through that lens, human intervention will hamper these systems and make them less effective. The rise of chess engines are the perfect example of this. Allow a human to pair with stockfish and override stockfish's favored move at will. This combination will lose every single game to a stockfish-only opponent.
- logicchains 2y ago>AI won't need VSCode Why not? It's still going to be quicker for the AI to use automated refactoring tooling than to manually make all the changes itself.
- rybosworld 2y agoMaybe I should have said: AI already doesn't need VSCode, or any IDE at all.
- kragen 2y agoMaybe it would work better if it used an IDE rather than having to write flawless code without ever testing it?
- abecedarius 2y agoI tried something related today with Claude, who'd messed up a certain visualization of entropies using JS: I snapped a phone photo and said 'behold'. The next try was a glitch mess, and I said hey, could you get your JS to capture the canvas as an image and then just look at the image yourself? Claude could indeed, and successfully debugged zir own code that way with no more guidance. This was all in the default web chat UI.
- svilen_dobrev 2y agomaybe shifting the jobs' target.. to higher a level (finally!) ? Reminds me of: https://chris-granger.com/2015/01/26/coding-is-not-the-new-literacy/ https://chris-granger.com/2015/01/26/coding-is-not-the-new-l... modelling has been , is , and will be the needed literacy..
- n144q 2y agoThat's the naiveity of software engineers. They can't see their limitations and think everything is just a technical problem. No, work is never the core problem. Backlog of bug fixes/enhancements is rarely what determines the headcount. What matters is the business need. If the product sells and there is no/little competition, the company has very little incentive to improve their products, especially hiring people to do the work. You'd be thankful if a company does not layoff people in teams working on mature products. In fact, the opposite has been happening, for quite a while. There are so many examples out there that I don't need to name them.
- whiplash451 2y agoThe main problem is that engineers in the Western world wont get to see the benefits themselves because a lot of Western companies will outsource the work to AI-enabled, much more effective developers in India. India and Eastern EU will win far more (relatively) than expensive devs in the US or Western EU.