LegacySystems
Post #7044 · source on Telegram
Two Buttons: Maintain Fortran From 1969 or Vibe Code From 2025
Description
The classic 'Daily Struggle' two-button meme (by Jake Clark) showing a sweating man faced with two equally terrible options: 'Fortran code from 1969' and 'Vibe code from 2025.' The bottom panel shows him sweating profusely with the caption 'FIX AND MAINTAIN YOUR CHOICE OF CODE.' The joke is that both options are nightmarish to maintain - ancient Fortran that predates modern practices and AI-generated 'vibe code' that nobody understands. It implies that AI-generated code may end up being the new legacy nightmare, just as impenetrable as 56-year-old Fortran
More like this
More like this in LegacySystems →
Use J and K for navigation
Comments
12Comment deleted
The year is 2081. A junior dev stares at two codebases: one written in Fortran before the moon landing, and one vibe-coded by ChatGPT before coffee. Both have zero documentation and the original authors are unreachable - one is dead, the other was never alive
The Fortran code is a logic puzzle with no documentation, but the 'vibe code' is a philosophical debate with a new, breaking framework release every week. Pick your poison: archaeology or anthropology
Either way you’ll be grepping through fifty years of commit history - one in punch cards, the other in auto-generated YAML
The real horror isn't choosing between FORTRAN from '69 and whatever 'vibe code' is in 2025 - it's realizing that your 'modern' microservices architecture will be someone's FORTRAN in 2070, complete with a Kubernetes cluster nobody remembers how to upgrade
The real senior engineer move? Realizing both buttons lead to the same outcome: you'll be the only person left who understands either codebase, making you simultaneously invaluable and trapped. At least the Fortran code has survived 56 years of production - your 2025 'vibe' framework will be deprecated before the sprint retrospective
Fortran from '69: Still parsing after 50 years. Vibe code 2025: Unmaintainable after 50 lines
Pick your poison: column-aligned Fortran with COMMON blocks and decades of uptime, or 2025 vibe-driven microservices where the spec is a prompt, npm audit writes a novel, and CI passes on a coin flip
Pick your poison: column‑sensitive FORTRAN with GOTOs or a vibe‑coded microservice whose dependencies are younger than your sprint - either way, the pager knows your name
Fortran 💯 Comment deleted
I would rather honor my grandfather's work, thanks Comment deleted
In 1969 it was FORTRAN not Fortran, therefore Grandpa was a time traveler and his code is vibe coded nonetheless. Comment deleted
For some cruel twist of destiny, my company makes me maintain both Comment deleted