No Complaints

The eternal shortcut of the desperate developer. You're asked to fix lint errors in a merge request, but instead of actually fixing the underlying code issues, you just slap an eslint-disable-next-line comment and call it a day. It's like putting a piece of tape over your check engine light and considering the car "fixed." Sure, the PR will pass now, but we all know what you did... and we've all done it too when deadlines loom. Technical debt? That's a problem for future you!

Content So you are a front end web developer Centre a div without the help of google ProdrammerHumor.io

Content Computer programming Kat Maddox ctrishifti me: why isn't this working? normal languages: you screwed up over here me: oh thanks me: why isn't this working? javascript: me: please i'm begging you javascript:

Content Stephen Gower As someone who has been developing websites since NCSA Mosaic was the only browser available, I'd just like to say that I'm really fcking tired of all the smart assholes out there continuously developing entirely new ways to build web applications. It started simple enough, just html and javascript. Then Cold Fusion. Then java applets. Then java servlets. Then 5 or 6 different Java application servers, EJBs, JSP, struts, XSLT, PHP. But screw all of that. We need Spring. No wait, we need Ruby.and Rails. Wait, we need Query. screw Query. We need AngularJs, and Backbone, and Ember! The world just won't be right until we have 12 different ways to do the same thing in Javascript! Forget all those server-side things you learned. Node js is here! No-wait. F'ck Node. Use Google Go! Honestly how many times are we going to re-invent this wheel? Unless you stay current with all of this nonsense, you basically become unhireable. I'm sure some of you 20 and 30-somethings have already experienced some of this fatigue. Now just imaging 10-15 more years where every 3 years a good portion of what you learned before is now obsolete, and you'll feel like I do.

Dehydrated developer crawling through a desert, passes by a Java water stand only to keep crawling toward JavaScript instead. The eternal battle of preferences continues! Some devs would literally risk heatstroke before touching certain languages. The irony is beautiful - Java and JavaScript are as related as car and carpet, yet the exhausted dev's loyalty remains unshaken. That's commitment to your tech stack that borders on clinical insanity. Next frame: same dev bypassing React for jQuery because "it's vintage."

Content DEV Q Create account Exciting Cade with JS A FUN EXPERIMENT!!! Siddhant Khare Posted on 12 May 4 1 Executing C Code with JavaScript