Programmer Humo Ur

Content Steve Maine smaine TIL that changing random stuff until your program works is "hacky" and "bad coding practice" but if you do it fast enough it's "MachineLearning" and pays 4x your current salary 6:40 PM 10 May 18 629 Retweets 1,692 Likes 17

Content A Common Mistake! A B2 Alice and Bob can complete a job in 2 hours. A C3 Alice and Charlie can complete the same job in 3 hours. BC4 Bob and Charlie can complete the same job in 4 hours. 2(A B C) 9 A B C 92 4.5 They take 4.5 hours working together. Mind Your cal Decisions But this makes no sense! When three people work together, it should take less time than when only two people work. But 4.5 hours is more time. So this answer must be wrong; the equations were set up incorrectly. pac1261 1 vear ado p 6 49K REPLY I work in software development, and everyone in that field knows that the more programmers you assign to a task, the longer it will take.

Content LOOKS LIKE YOU WERE PRESCRIBED A PLACEBO WHAT'S A PLACEBO? SOMETHING THAT DOESN'T WORK, BUT TRICKS PEOPLE INTO THINKING IT DOES (IM A PLACEBO? IC SPO SORED BY ERIK BLO MRLOVENSTE

Content css colour: darkgrey css colour: grey

Content People who are into tech People who make tech ProdrammerHumor.io

Content There's a repo on Github containing some scripts used by a tech employee that his coworkers discovered after he left the company. Here's a summary of his shenanigans: 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 well gonna 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 I'm keeping those Reply 4 10.3k J