It Works On My Machine

Content Dev moved user-story to in-progress Dev added sub-tasks to user-story Dev closed all sub-tasks, uploaded acceptance criteria documentation, created functional tests with results and resolved the story. WF ProarammerHumor.io

The eternal struggle of every developer who knows better but chooses chaos anyway. Sure, debuggers exist with their fancy breakpoints and variable inspection, but there's something primitively satisfying about littering your code with print("HERE") , print("WHY GOD WHY") , and the classic print("AAAAAAAAAAA") . It's like using a stone axe when you have a chainsaw in your garage. We all know we should use proper debugging tools, but smashing that red button and turning our console into a Jackson Pollock painting of random values just hits different. Proper debugging techniques? In this economy?

Coding something and understanding it for exactly 2.7 seconds before it becomes an indecipherable mess? That's the universal developer experience. You write some brilliant hack at 2AM, feeling like a genius, only to return later wondering if your cat actually wrote it while walking across your keyboard. The worst part? That code somehow runs perfectly in production, and you're now terrified to touch it because it's held together by digital duct tape and prayers. Documentation? That would've been a great idea... yesterday.

Content I Am Devloper iamdevloper 39m Dec. 27, 2017 10:23:50 AM V shoutout to all the devops people currently on their parent's wift trying to fix a database issue in production via Twitter Web Client 11 341 Retweets 953 Likes

Content Write code The tests fail Write more tests to narrow down the problem Write tests The tests fail Those tests pass The bug was in the test

Content 62.5k S) rAskReddit Posted by uSixty Saints 6 hours ago 83 5 2 JOIN Girls who took notes using 50 different colored pens, where are you now? Do you still continue to write using all those colors? 4 6.1k Comments Share A Save Terminal - profile (etc) - VIM File Edit View Terminal Tabs Help 1 etcprofile 3 Set our umask 4 umask 022 6 Set our default path 7 PATH"usrlocalsbin:usrlocalbi :usrbin" 8 export PATH 10 Load profiles from etcprofile.d 11 if test -d etcprofile.d; then 12 for profile in etcprofile.d sh; do 1 System-wide bashre file for intel ractive bash(1) shells. 3 To enable the settings commands in this file for login shells as ell, 4 this file has to be sourced in e tcprofile. If not running interactively, don do anything 7 -z "PSI" return 9 check the window size after each 13 test -r "sprofile" "spr command and, if necessary, 14 15 16 fi 17 ofile" done unset profile 10 update the values of LINES and CO LUMNS. 11 shopt -s checkwinsize 12 13 set variable identifying the chro 18 Source global bash config ot you work in (used in the prompt below) Vetcprofile ROJ Top cbash.bashrc ROJ Top "etcprofile" (readonly 27L, 541C