The Calm Before The TypeScript Storm

Content Boss says to build a web app in IS and React Boss: "Why isn't this in Nextis? This should use Nextis.' I spend 10 hours refactoring rewriting Boss: "Why isn't this in TypeScript? This should use TS." ProarammerHumor.io spend 20 hours on the first set of reas Boss: "Why isn't this in Nextis? This should use Nextis." I spend 40 hours on the next set of reas Boss: "Why isn't this in TypeScript? This should use TS."

Content Pimples? Blackheads? Runtime errors since switching to Typescript? ProdrammerHumor.io Zero Zero ZERO

Ah, the classic "beginner's paralysis." Remember when learning to code was just picking up a book on BASIC or Pascal? Now it's like walking into a pharmacy with 47 different cold medicines when all you wanted was something to stop your runny nose. The tech industry has perfected the art of reinventing the wheel every six months, leaving newbies staring at a buffet of languages and frameworks with absolutely no idea which one won't be obsolete by the time they finish the tutorial. Pro tip from someone who's been coding since punch cards: just pick one and start. The second language is always easier, and the twentieth barely registers as new. Meanwhile, the industry will keep churning out shiny new options like a slot machine that only pays in technical debt.

Content JIS DAILY JavaScript Daily JavaScriptDaily 1h Next gen thinking over on Reddit. - Brilliant-8148 11 points 4 days ago I use typescript, but I declare everything as an any because I love the flexibility permalink embed save report reply CharlesStover 8 points 4 days ago This is unironically better than not using TypeScript at all. permalink embed save parent report reply - Brilliant-8148 4 points 4 days ago I know, for my resume! permalink embed save parent report reply 17 8 88 14 10.3K 1 Coderman unlocomax - I use seatbelt but I pass it behind my back because I love the flexibility - This is unironically better than not using SeatBelt at all. -I know, for highway patrol! 11:49 AM Sep 13, 2023 112 Views

OH. MY. GOD. The absolute AUDACITY of this prompt! "Change this ENTIRE repository to TypeScript. Make NO mistakes." As if converting a JavaScript codebase to TypeScript is just a cute little afternoon activity! 💀 It's giving "I need this by EOD" energy while casually requesting you to rewrite potentially THOUSANDS of files without a SINGLE type error. The "make no mistakes" part is just the chef's kiss of delusion. Like, honey, even TypeScript itself has bugs, but sure, I'll just casually perform FLAWLESS type inference on an entire legacy codebase. Should I also solve world hunger in the next commit?

Content TYPESCRIPTIAVA SCRIPT JENKINS GIT OTHER STYLING LANGUAGE (SASS) FRAMEWORK HIPSTER ME AS JUNIOR DEV AND BARELY UNDERSTAND FRONTEND DEVELOPMENT ingfip.com