Ah, the classic "I'll fix it later" comment that's been sitting there since 2019. The code has an if-else statement that does exactly the same thing in both branches. Someone probably spent hours debugging why their overloaded function wasn't working, then just gave up and wrote this abomination with a promise to fix it "when TypeScript understands overloading well enough." Spoiler alert: they never fixed it, and three devs have since quit rather than touch this cursed file.
Context In Comments
1 month ago
187,068 views
0 shares

typescript-memes, technical-debt-memes, code-comments-memes, if-else-memes, overloading-memes | ProgrammerHumor.io
More Like This
Cobol for Your Monies
3 years ago
94.0K views
0 shares

Runtime Css
2 years ago
38.2K views
0 shares

Family Life For Programmers
1 month ago
227.0K views
1 shares

The Unholy Trinity Of Programming Errors
4 months ago
159.9K views
0 shares

The Dramatic Birth Of TypeScript
3 months ago
113.7K views
0 shares

I think my GitHub is trying to tell me something...
3 years ago
93.3K views
0 shares

Loading more content...