Skip Navigation

The Dumbest Move in Tech Right Now: Laying Off Developers Because of AI

ppaolo.substack.com

The Dumbest Move in Tech Right Now: Laying Off Developers Because of AI

111 comments
  • This is so fucking sad to acknowledge that a lot of people just want to squeeze any profit left in the industry, even though they know AI is a great tool for developers, not a replacement. They must know that because anyone who can access it can replicate the same things, making these products uncompetitive.

    • AI is a great tool for developers, not a replacement

      AI isn't a great tool for developers. It's a great tool for mitigating the knowledge gap between an individual's academic understanding of a development project and the syntax involved in the language they are attempting to deploy.

      As the number of programming languages has proliferated faster than the volume of developers versed in each language, and the older languages have lost much of their professional base to retirement and layoffs, we've needed increasingly elaborate tools to fill in the skills gaps.

      But AI doesn't fix the underlying problem of an increasingly large backlog of code desperately in need of refactor or replacement. It just papers over the problem with a cheat-sheet of simple conversions that junior developers can leverage to liter the next iteration of the codebase with bandaids.

      A proper solution to our coding backlog would be educational first and foremost. We need more rigorously enforced orthodox approaches to coding. We need more backwards compatibility between systems. We need to refine the number of languages in active use and narrow the size and scope of their libraries. We need a more universalist approach to building and maintaining database schemas, digital communications, and business practices. We need a publicly funded open source community of developers to build the backbone of software into the 21st century.

      What we're producing is the opposite of that. Less rigor. Fewer recognizable standards. Less training. Poorer code hygiene and weaker enforcement of best practices. More bugs. So many more bugs. And enormous volumes of legacy code that nobody will be able to maintain - or even understand - in another twenty years.

  • Even if AI is an actual tool that improves the software development speed of human developers (rather than something that ends up taking away in time spending reviewing, correcting and debugging the AI generated code, the time savings it gives in automatically writing the code), it's been my experience in almost 30 years of my career as a Software Engineer that every single tooling improvements that makes us capable of doing more in the same amount of time is eaten up by increasing demands on the capabilities of the software we make.

    Thirty years ago user interfaces were either CLI or pretty simple with no animations. A Software Systems was just a software application - it ran on a single machine with inputs and outputs on that machine - not a multi-tiered octopus involving a bunch of back end data stores, then control and data retrieval middle tiers, then another tier doing UI generation using a bunch of intermediate page definition languages and a frontends rendering those pages to a user and getting user input, probably with some local code thrown into the mix. Ditto for how cars are now mostly multiple programs running of various microcontrollers with one or more microprocessors in the mix all talking over a dedicated protocol. Ditto for how your frigging "smart" washing machine talking to your dedicated smartphone app for it probably involves a 3rd machine in the form of some server from the manufacturer and the whole thing is running over TCP/IP and using the Internet (hence depending on a lot more machines with their dedicated software such as Routers and DNS servers) rather than some point-to-point direct protocol (such as Serial) like in the old days.

    Anyways, the point being that even if AI actually delivers more upsides than downsides as a tool to improve programmer output, that stuff is going to be eaten up by increasing demands on the complexity of the software we do, same as the benefits of better programming languages were, the benefits of better IDEs were, of the widespread availability of pre-made libraries for just about everything were, of templating were, of the easiness to find solutions for the problem one is facing from other people on the Internet were, of better software development processes were, of source control were, of colaborative development tools were and so on.

    Funnily enough, for all those things there were always people claiming it would make the life of programmers easier, when in fact all it did was make the expectations on the software being implemented go up, often just in terms of bullshit that's not really useful (the "smart" washing machine using networking to talk to a smartphone app so that the machine manufacturers can save a few dollars by not putting as many physical controllers in it, is probably a good example)

  • I'm 90% sure it's something to do with the stock market, buy backs and companies having to do cryptic shit to keep up with a fake value to their shares

  • AI-assisted coding […] means more ambitious, higher-quality products

    I'm skeptical. From my own (limited) experience, my use-cases and projects, and the risks of using code that may include hallucinations.

    there are roughly 29 million software developers worldwide serving over 5.4 billion internet users. That's one developer for every 186 users,

    That's an interesting way to look at it, and that would be a far better relation than I would have expected. Not every software developer serves internet users though.

111 comments