Please Don't Make Me Go Back There

The evolution of web development in four panels! Started with the innocent dream of "build the internet" - so pure, so simple. Then we added some HTML/CSS because, you know, websites should look pretty. But then... oh no... the JavaScript framework apocalypse struck! Now we're all frantically learning 17 new frameworks before breakfast just to stay employable. Remember when you could just FTP a single HTML file to a server and call it a day? Now you need 4GB of node_modules to display "Hello World". The modern web: where your simple todo app requires more computing power than NASA used to reach the moon.

Two booths at the programming convention. The if-else booth has a massive line wrapping around the block. The switch case booth? One lonely soul sitting there wondering where it all went wrong. Developers will write seventeen nested if-else statements before even considering a switch case. It's like we collectively agreed that readability is optional and we'd rather chain conditionals until our IDE starts crying. Switch cases are sitting there being perfectly optimized for multiple discrete values, but nah, let's just keep stacking those else-ifs like we're building a Jenga tower of technical debt. The switch case deserves better. It's faster, cleaner, and doesn't make your code look like a sideways pyramid. But here we are, loyal to if-else like it's 1972.

Junior dev asks for style guidance. Senior dev smugly says "just use common sense." Junior dev politely asks for actual linter config. Senior dev proceeds to forcefully inject "common sense" directly into their brain, which apparently translates to "whatever the LLM and linter say." Because nothing screams "common sense" like blindly following ESLint's 47 warnings about semicolons while your production server is literally on fire. The real kicker? Everyone's "common sense" is wildly different. One person's common sense is 2-space indentation, another's is tabs, and a third person's involves sacrificing a rubber duck to the code gods before every commit. Just give them the .eslintrc file, Karen. It takes 30 seconds and saves everyone from the philosophical debate about whether trailing commas are a war crime or a gift from the heavens.

Ah, the eternal naming convention war presented as a scholarly lecture. The first variable name struts around in camelCase (first word lowercase, subsequent words capitalized), while the second flaunts its PascalCase elegance (all words capitalized). Meanwhile, developers in the audience are silently judging each other's preferences while pretending their chosen style is objectively superior. The real joke? We'll spend 45 minutes arguing about this in code reviews but accept variable names like 'x' and 'temp' without blinking.

Content I requests Issues Marketplace Explore D Overview Repositories 2 F Projects Packages Stars Pinned A MikeOtropicMeetupFood A script to map different meetups and the food they offer TypeScript MikeOtropicGitBlameHeritage Git Blame extension to balr JavaScript 2,130 contributions in the last year BOBBER Mike Ron MikeOtropic B000 Follow 23 7 followers 1 following A MikeOtropic Israel How2App.com 25 Code Blaming Contribution activity March 2022 A 81 contributions in private repositories 2020 2019 2018 2017 2016 2015 2014

First panel: JavaScript behaving like a normal language where string + string = concatenated string. Second panel: JavaScript on crack where '2'+'2' = 100 and "Hello"+2 = "llo". The true horror of JS type coercion in its natural habitat. What kind of sadistic language designer thought "yes, let's make + sometimes concatenate and sometimes convert strings to numbers based on my mood today"? This is why senior devs have that thousand-yard stare during code reviews.