this post was submitted on 30 May 2026
-42 points (26.7% liked)

Technology

85055 readers
2452 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] timochka@lemmy.zip 0 points 2 days ago (1 children)

He may be dead right, and unduly pessimistic at the same time.

The industry massively overhired relatively unskilled people who believed the job was "writing code", for a few decades; those people got by thanks to Stack Overflow and the fact that most of the code that needed writing really didn't need much skill anyway. There's very little innovation or engineering in most business platforms - a couple of decent architects and an army of code monkeys can deliver most of the software that's needed. We also developed programming languages and frameworks that made it much easier for the unskilled developers to be productive.

Sad to say, these are the people now loudly wailing about the iniquities of AI. If you thought churning out code was the profession - you absolutely should be very concerned that AI will replace you - it will. But if you realised that code was only ever a side effect of the job, which was applying computing to solve problems - you have little to worry about. AI is just a new tool to do it, and is no more a threat than optimising compilers, mamaged runtimes or IDEs were.

When I started my career, I wrote assembly code by hand for platforms that barely even had an operating system. Then C. Then Java - and as far as I'm concerned, every programming language since then has pretty much had training wheels permanently attached... For the last few years, I've preferred Rust, although the job has been more about developing architectures for others to implement than coding myself. But my expectation is that I'll end my career writing instructions for AIs to implement; and that's absolutely fine. The job didn't change, just some of the intermediate representations I had to write to do it. The profession will probably go back to look more like the one I entered - fewer people doing it, but with more formal education in computer science, and much less "coding".

Which is not to say I don't think there's anything to worry about for the profession, there absolutely is. How the hell we identify the future senior engineers with the actual skill and aptitude required, when there are no junior roles to provide the necessary apprenticeship - and when the education system is struggling to adapt to AI use in class - is a massive and fundamental problem. That's what keeps me awake at night, not people who think writing CRUD APIs in C# is a divine gift.

[โ€“] tomalley8342@lemmy.world 0 points 1 day ago

Yep, and in 5 years architects and tech leads will be similarly be made obsolete. In the end, if you want to make money, all technology decisions are just implementation details in service of what actually matters - delivering business value. Therefore the only stable career in the age of AI is the project manager.

lol