Give your POVs

Content On a github repo press the period key (.) on your keyboard to Load VSCode on your browser. Untill we meet again gp1-3.0 ll anyfactor

Content Ben Awad odpowiedziata Catalin Pit catalinmpit 1 dzien Working with JavaScript is like looking both ways before you cross the street, and then getting hit by an airplane. 53 17 438 O 2418 Ben Awad benawad 12 g. TypeScript is like vour own personal assistant that warns you when airplane is coming 7 17 11 M 156

Content UN i hate the backend! hate the backend! UN we've got you surrounded! come WOrK on node.is

So you thought setting your date of birth validator to accept anyone under 150 years old was being GENEROUS and INCLUSIVE? Congratulations, you've just granted Pharaoh Ramesses II a valid passport in 1976. The man died in 1303 BC and somehow your validation logic was like "yeah, seems legit, he's only 3,279 years old, well within our acceptable range!" This is what happens when developers write validation rules at 2 PM on a Friday thinking "nobody will EVER need to enter a date that old." Meanwhile, Egypt's out here issuing official government documents to mummies for restoration trips to France, and your form is just nodding along like "welcome aboard, your majesty." The real kicker? Someone at the Egyptian passport office in 1974 had to manually enter "-/+/1303 BC" into whatever system they were using, and it WORKED. Edge cases aren't just theoretical anymore when you're dealing with royalty that's been dead for three millennia. Maybe next time set that validation to "must be alive" instead of just "reasonably old."

Some developers just want to watch the world burn. Instead of implementing a standard phone input field, this diabolical programmer created a SLIDER for entering a phone number. Pure evil genius at work! This is what happens when you give developers too much free time and not enough code reviews. The next sprint planning will definitely include a "fix that damn phone input" ticket with highest priority.

Running npm update on a Monday morning is basically playing Russian roulette with your entire codebase. You're sitting there all confident, thinking "I'll just update these dependencies real quick," while your coworkers watch in horror knowing exactly what's about to happen. One second everything's fine, the next second you've got 47 breaking changes, your build fails, half your tests are red, and that one package decided to jump from version 2.1.4 to 87.0.0 because semantic versioning is apparently just a suggestion. Your coworkers have seen this movie before—they know the next 3 hours of your life will be spent in dependency hell trying to figure out why node-sass won't compile anymore. Pro tip: Always run updates on Friday afternoon so you have the whole weekend to contemplate your life choices. Just kidding—never update on Friday. Or Monday. Actually, maybe just never update.