Ah yes, the classic "let's handle years with a switch statement" approach. Some poor developer back in 1999 was like:switch(year) {
case 2020: // pandemic mode
case 2021: // still pandemic
case 2022: // recovery mode
case 2023: // normal-ish
case 2024: // election chaos
// TODO: add more years later
default: trainControl.panic();
}
And then they quit, got promoted, or died before anyone remembered to add 2025. Twenty-five years after Y2K and we're still writing software like time is a finite concept. This is why we can't have nice things... or functioning trains, apparently.
Ok Who Forgot To Put 2025 In The Switch Statement
11 months ago
294,032 views
0 shares
y2k-memes, legacy-code-memes, switch-statement-memes, date-handling-memes, software-failure-memes | ProgrammerHumor.io
More Like This
Just studying but already can relate
2 years ago
58.9K views
0 shares
Good luck enforcing your bullshit
2 years ago
56.8K views
0 shares
Nuclear Chain React
11 months ago
275.5K views
0 shares
Dear IDE, Let me breath...
1 year ago
51.6K views
0 shares
She got the point..
1 year ago
57.6K views
0 shares
This is what happens when you hardcode time
2 years ago
56.7K views
0 shares
Loading more content...
AI
AWS
Agile
Algorithms
Android
Apple
Bash
C++
Csharp