Test-Driven Development

Content CLAUDE AND CHATGPT CROSS-CHECKING EACH OTHER IDE WITH LINTERS, LSP, SAST AND 50 OTHER PLUGINS AN ENTIRE CLUSTER ON STANDBY FOR PARALLEL TESTS -TERMINAL -VIM (OPTIONAL) PARIS 202 2024 Tory 3 42 3 38 Yell KIM SIR YANG SERIES 10 10

Content Based on a true story: xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that. xxx: So we're sitting here, looking through his, uhm, "legacy" xxx: You're gonna love this xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login. xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help" "trouble" "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time". xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling wellgonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am. xxx: (and the oscar goes to) fucking-coffee.sh - this one waits exactly 17 seconds (!), then opens a telnet session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has a TCP socket up and running) and sends something like sys brew . Turns out this thing starts brewing a mid-sized half- caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk. xxx: holy sht l'm keeping those

Content Junior who broke production Random senior You've seen this before?! 11 times, as a matter of fact ProdrammerHumor.io Marianita.co

Content Finding your code in a java project be like: Actual fucking code projectsrc projectsrctest projectsrctestjava projectsrctestjavaclasswrapper projectsrctestjavaclasswrapperclass proiectsrctestjavaclasswrapperclasssubclass

Ah, the two eternal states of developer existence. First panel: code doesn't work and you have no idea why. Second panel: code suddenly works and you have even less idea why. The universe maintains balance by ensuring that understanding remains equally elusive in both failure and success. Just another day where blind luck trumps actual competence. At least the confusion is consistent.

Content Python's GIL Removal Reveals Second, Stronger GIL Behind It For many years, the Python GIL has been the target of criticism for being a bottleneck in multi-threaded performance. Countless workarounds and promises of its removal have been part of Python development folklore. However, when the Python core development team finally unraveled the notorious lock in the latest experimental build, what lay underneath was beyond anyone's wild speculations - a secret, second-layer GIL of herculean strength. "Discovering the second GIL not only nullifies all our multi-threading gains but actually puts us at a greater concurrency disadvantage than before." said leading Python contributor Dr. Ana Lepton. " It's like finding a secret boss in a video game that's harder than the final boss." Others, however, see it as a challenge. "We've faced the first GIL before, and we can face the new one too," ProdrammerHumor.io