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
3 months ago
241,213 views
0 shares

typescript-memes, technical-debt-memes, code-comments-memes, if-else-memes, overloading-memes | ProgrammerHumor.io
More Like This
Typescript gang
4 years ago
99.3K views
0 shares

Now You Know
2 months ago
222.5K views
0 shares

No comment
1 year ago
321.4K views
0 shares

The Hierarchy Of Programming Pain
6 months ago
213.0K views
0 shares

The Difference Between 0 And Null
7 months ago
189.4K views
0 shares

The Missing Function Call Revelation
4 months ago
165.1K views
0 shares

Loading more content...