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
5 months ago
319,430 views
0 shares
typescript-memes, technical-debt-memes, code-comments-memes, if-else-memes, overloading-memes | ProgrammerHumor.io
More Like This
Await My Death
3 months ago
194.4K views
0 shares
Runtime Css
2 years ago
74.2K views
0 shares
These job requirements are getting out of hand
2 years ago
363.0K views
0 shares
The Compiler's Complete Meltdown
3 months ago
316.5K views
0 shares
Be Ungovernable: TypeScript's Yellow Card
8 months ago
205.0K views
0 shares
Outsourcing Your TypeScript Migration To The Real Senior Engineer
2 months ago
253.1K views
0 shares
Loading more content...
AI
AWS
Agile
Algorithms
Android
Apple
Bash
C++
Csharp