The four-word status question every engineer secretly fears in sprint reviews

Description

The meme is a screenshot of a Twitter exchange on a white background. First tweet: “Sabrina @sabrinaesaquino · 15h Make a programmer cry with 4 words” followed by reply, retweet, and like counts (2 690 replies, 737 retweets, 3 365 likes). Below, a threaded response shows the profile of “Lorin Hochstein @norootcause” saying: “How close to done?” in quotation marks. Both profile photos are blurred for anonymity, and a small watermark in the lower-left corner reads “t.me/dev_meme”. The humor plays on the perennial pain of engineers being pressed for precise completion estimates during project status meetings, highlighting deadline pressure and management expectations in software development culture

Common Tags

DeadlinePressure ProjectDeadlines ManagerExpectations StakeholderPressure DeveloperHumor Management MisalignedExpectations DeveloperFrustration RelatableHumor DeveloperReality

Comments

Anonymous ★ Top Pick ‘How close to done?’ - the quantum observation that converts the remaining 10% into 90% compliance docs, edge-case fixes, and integration entropy

Anonymous ★ Top Pick

‘How close to done?’ - the quantum observation that converts the remaining 10% into 90% compliance docs, edge-case fixes, and integration entropy
Anonymous

The only thing more terrifying than 'How close to done?' is realizing you've been at '90% complete' for the last three sprints, and the remaining 10% contains all the edge cases, integration issues, and that one requirement buried in email thread #47 that nobody remembered until yesterday's demo
Anonymous

The four most terrifying words in software engineering aren't 'production is on fire' - they're 'how close to done?' Because the honest answer requires explaining why your 90% complete feature has been 90% complete for three sprints, why 'done' depends on whether we're counting the edge cases you just discovered, the refactoring you know you should do, the tests you haven't written, the documentation that doesn't exist, and whether 'done' means 'works on my machine' or 'actually deployable.' It's the question that forces you to confront the uncomfortable truth that software estimation is fundamentally a dark art practiced by optimists who haven't learned to account for the fact that the last 10% takes 90% of the time
Anonymous

“How close to done?” - translation: convert unknown unknowns, cross‑team dependencies, and the legacy SOAP endpoint into a single percentage a status slide can pretend is real
Anonymous

It's 90% done - has been for months; the last 10% observes Zeno's paradox under Parkinson's law
Anonymous

Percent-complete is a Heisenberg variable - once you measure it, integration exposes three unknown unknowns and you’re suddenly negative 20% done
@N1KD1 4y

Unresolvable git merge conflict
@QutePoet 4y

sudo rm -rf *
1. @DavidGarciaCat 4y
  
  suggesting / instead of *
  
  @QutePoet 4y
  
  There is no surprise with /, but * can be intrigue! Programmer gonna cry finding what he have deleted. And deleting /etc and /usr/bin is enough to kill working Linux installation.
  
  @DavidGarciaCat 4y
  
  Faig enough 😄
2. @NevermindExpress 4y
  
  rm -rf / —no-preserve-root
  
  @QutePoet 4y
  
  That's longer than 4 words if you count parameter as word.
@DavidGarciaCat 4y

how long will take
@devil_with_a_grudge 4y

[ $[ $RANDOM % 6 ] == 0 ] && rm -rf --no-preserve-root / || echo *Click*
@SamsonovAnton 4y

sudo find . -name '.*' -delete NB. Don't try this at $HOME.