True Happiness

The Chernobyl control room energy is strong with this one. Someone suggests rolling back the production deployment, another asks what they'd even roll back to, and the third guy drops the real truth bomb: nobody has a clue what's running in prod right now. Classic "move fast and break things" taken to its logical conclusion. You've shipped so many hotfixes, patches, and "temporary" solutions that the production environment has become a beautiful mystery box. Git history? Deployment logs? Documentation? Those are for teams that aren't living on the edge. The title says it all—Ship First, Understand Never. Why waste time understanding your codebase when you could be shipping features? Rollback strategies are for people who remember what they deployed in the first place.

Content when you find what the problem with vour code is after 6 hours of debugging and realise it's a spelling mislake made with mematic ProdrammerHumor.io

Content PROBLEM: JAVASCRIPT HAS ALMOST NO STANDARD LIBRARY SOLUTION: THOUSANDS OF COMMUNITY -SUPPORTED LIBRARIES OF WILDLY VARYING QUALITY PROBLEM: JAVASCRIPT HAS NO PACKAGING OR A LINKER TO TIE THESE PACKAGES TOGETHER PROBLEM: JAVASCRIPT WON'T RUN OUTSIDE THE BROWSER SOLUTION: V8 PROBLEM: JAVASCRIPT IS SINGLE -THREAD BY DESIGN SOLUTION: ASYNCHRONOUS PROGRAMMING, NODE. JS PROBLEM: CALLBACK HELL PROBLEM: PROTOTYPAL INHERITANCE IS PANTS -ON- HEAD STUPID THAT'S RIGHT, I SAID IT. PROBLEM: WEB RESOURCES NEED TO BE MINIFIED AND ZIPPED FOR PERFORMANCE PROBLEM: THE DOM IS TOO SLOW FOR VIDEO GAMES SOLUTION: CANVAS PROBLEM: JAVASCRIPT IS TOO SLOW FOR VIDEO GAMES SOLUTION: USE AN ASSEMBLY- LIKE SUBSET OF JAVASCRIPT CALLED ASM.JS PROBLEM: ASM.JS IS BASICALLY UNWRITABLE 4 HUMANS. SOLUTION: COMPILE A BETTER LANGUAGE TO JAVASCRIPT (C, EMASCRIPT 2016, COFFEESCRIPT, JSX) SOLUTION: HUNDREDS OF COMMUNITY SUPPORTED BUILD TOOLS OF WILDLY VARYING QUALITY PROBLEM: GRUNT. SOLUTION: GULP PROBLEM: GULP PROBLEM: MACHINE GENERATED OUTPUT IS MORE DIFFICULT TO DEBUG PROBLEM: ASYNC IS STILL A NIGHTMARE, HUH? PROBLEM: BALLOONING PROJECT SIZE AND COMPLEXITY PROBLEM: JAVASCRIPT STILL DOESN'T DO EVERYTHING PROBLEM: OUTPUT RUNS VERY SLOWLY ON MOBILE DEVICES SOLUTION: ELECTRON, PHONEGAP, FIREFOXOS HOW IS DIGGING GOING TO GET US OUT OF THIS HOLE? WHERE I AM FROM, THE POINT OF DIGGING IS NOT FREEDOM FROM DIGGING

Expectation: Writing elegant code with perfect structure and original logic. Reality: WHEEEZE *frantically searching through 2000 lines of code at 3am* "I FORGOR SEMICOLON" And then there's that one missing semicolon that keeps you awake for 4 days straight while your non-programmer friends think you're being dramatic. No, Chad, this isn't like when you "missed her" - this is psychological warfare between me and a punctuation mark that Satan himself invented.

Ah, the classic CS exam paradox! Nothing says "I understand programming" like frantically scribbling syntax on dead trees while praying your indentation looks right without an IDE. Meanwhile, in the real world, we're all just professional Googlers with Stack Overflow PhDs. The irony that the guy holding the sign built a billion-dollar empire without ever having to pass a whiteboard algorithm test on paper is just *chef's kiss*. Next up in university curriculum: "Writing HTML with quill and parchment" and "Debugging without actually running the code because reasons."

Content C A programming language for Real Men. Most languages try to provide a simplified way to solve specific problems well. C makes no such concession and tries to be mediocre at everything. It lets you program at a very high level, and a very low level in the same program. It lets you write procedural code, object oriented code, generic code and mix them all up. It makes you decide everything and provides no help if you get it wrong. It is by far the biggest, most complicated, ugly, down-right dangerous language you can use. But it does run fast. It takes at least twice as long to program in C as any other major language (except C). The men who program in C are Real Men. The women who program in C are Real Men too. You can spot a C programmer from their testosterone fueled swagger, and the unbelievable amount of contempt they inject into the phrase Java "programmer". They'll probably do the air quotes and all. Dev: 'Hey, Reg, you know C right? What does: "Isrc Cont. cpp(52) : error C2679: binary '': no operator found which takes a right- hand operand of type 'int' (or there is no acceptable conversion) C: Program Files Microsoft Visual Studio 8C include vector (392): could be 'std: VectoriteratorT, Alloc std:VectoriteratorTy, Alloc:operator (const std:VectoriteratorTy, Alloc' with TyMain::Cont, Allocstd allocator Main::Cont while trying to match the argument list (std::VectoriteratorTy, Alloc, int)'with TyMain::Cont, Allocstd::allocatorMain::Cont " mean?' Reg: 'You missed a semicolon at the end of the line.' ProdrammerHumor.io