The Recurring Cycle of AI Job Displacement Anxiety in Programming

Description

A three-panel stick-figure comic illustrates the cyclical fear among developers about AI. In the first panel, a character declares, "AI will take all of your jobs!", causing a group of figures representing TypeScript, Java, C, and Go to huddle in fear, with the Rust mascot (Ferris the crab) on top looking worried. In the second panel, a large figure gives a confident thumbs-up, seemingly dismissing the threat. In the final panel, the group returns to their initial state of huddled fear, showing the anxiety is persistent. The meme humorously captures the tech industry's recurring waves of panic and temporary confidence regarding job security in the age of AI, suggesting that even developers of "safer" languages like Rust are not immune to the existential dread

Common Tags

Rust AIHype AIHypeVsReality AI Java Golang TypeScript LanguageWars

Comments

Anonymous ★ Top Pick The three stages of AI adoption grief: 1. Panic. 2. A senior dev scoffs and gives a thumbs up after a single cherry-picked benchmark. 3. Back to panic when the AI starts suggesting code with unsafe blocks

Anonymous ★ Top Pick

The three stages of AI adoption grief: 1. Panic. 2. A senior dev scoffs and gives a thumbs up after a single cherry-picked benchmark. 3. Back to panic when the AI starts suggesting code with unsafe blocks
Anonymous

LLMs can spit out CRUD in 12 dialects, but ask them to placate Rust’s borrow-checker and they start hallucinating about garbage collection
Anonymous

After 15 years of hearing 'rewrite it in Rust,' we finally found the killer use case: Rust's borrow checker is so complex that even AGI gives up trying to understand lifetime annotations and moves on to easier targets
Anonymous

When someone suggests AI will replace developers, but you've spent the last six months fighting the borrow checker - you know no neural network has that kind of masochism built in. Rust developers aren't worried about AI taking their jobs; they're too busy explaining why their compile times are a feature, not a bug, and why memory safety without garbage collection is worth protecting at all costs. Besides, if AI could truly understand Rust's lifetime annotations, we'd have already achieved AGI
Anonymous

AI breezes through TS/Java/Go boilerplate; the moment lifetimes, Send/Sync, and a borrow-across-await appear, it hallucinates 'static' - so everyone pushes the Rust dev to the front
Anonymous

AI took TS, C#, Docker jobs - good luck explaining monolith-to-microservices migration without a 6-month outage
Anonymous

AI won’t take your job; Rust will claim ownership, Java will demand an interface, TypeScript will add types to the panic, C will wander into UB, and Go will spawn a goroutine to pretend it’s fine
@azizhakberdiev 1y

Recursive
@gongchanM1 1y

Can ai handle brainfuck or even whitespace? Probably no
1. @captain_gaga 1y
  
  Can you?
  
  @gongchanM1 1y
  
  I can only complain at the legacy code I need to deal with. Thats my job
  
  @captain_gaga 1y
  
  That's one thing that neural models will never replace, so you're safe there
2. dev_meme 1y
  
  Technically this is exactly the area where AI will excel much ahead of almost 100% of actual devs
@noi01 1y

Cant take a job if you dont have one - Rust bros
@ZgGPuo8dZef58K6hxxGVj3Z2 1y

Facts
@AmindaEU 1y

Are they emphatic too? How is Haskell itself, should I join? /S