Forced Into JavaScript: A Child's Nightmare

Content So what is it that you do, exactly? Junior JS Developer I'm responsible for our Node. js API layer. It's the layer where all our frontend and mobile applications consume the backend service. Also, I'm learning LLMs and Rust and Unity AR when I'm not on-call. Senior Backend Engineer I'm a Go developer in the core backend team. I own the features of our service mesh. Fellow Distinguished Principal Staff Engineering Technical Lead. Head of Dragons. First of his name Architecture PERMITIO

So you're checking if an email is already taken by sending it to the server, getting back a list of all registered emails , and then doing a client-side .includes() check? That's like asking the bank to give you everyone's account numbers just to verify yours doesn't exist yet. Not only is this a massive security vulnerability (congrats, you just leaked your entire user database to anyone with DevTools open), but it's also hilariously inefficient. Why return an array of potentially millions of emails when the server could just return a boolean? The backend dev is probably crying somewhere. The cherry on top? After doing all this client-side "validation," you're still showing success messages without any actual server confirmation. Chef's kiss of terrible architecture. 🤌

Ah, the duality of random number generation! The top panel shows the proper way—importing libraries like random , time , or os to generate proper pseudo-random numbers with good entropy. The bottom panel reveals the chaotic evil approach—hardcoding your "random" generator without external input, which is basically just saying return 4 because it was randomly chosen by fair dice roll. Guaranteed to be random! The twisted face in the second panel perfectly captures the deranged energy of a developer who thinks Math.floor(Math.random() * 6) + 1 is too much work and opts for const getRandomNumber = () => 4; instead. Cryptographers are screaming somewhere.

Your 300kb app casually carrying around a 12GB backpack of node_modules is the most accurate representation of modern JavaScript development. It's like buying a single screw from Home Depot and they hand you an entire warehouse. The ratio is genuinely insane. You install one package to check if a number is even, and suddenly you're downloading half the internet because that package depends on 47 other packages, which depend on 200 more packages, which all depend on different versions of the same utility library. Meanwhile, vanilla JS is just sitting there, lightweight and dependency-free, watching you struggle to push your project to GitHub because the node_modules folder is heavier than a black hole. Maybe those "just use vanilla JS" people had a point after all.

Content Overcaffeinated Fox DarrenPMeyer : I'm torn, because I know I'm supposed to get the second vaccine shot, but I'm also supposed to avoid sequel injection 9:16 PM 02 Mar 21 Twitter Web App 1,098 Retweets 147 Quote Tweets 5,786 Likes

Content Dami dakitidami.eth dakitidami - 10h The backend dev and the frontend dev