In inpatient psychiatry I tell my coworkers “I hope your shift is mind-numbingly boring” or something similar (keyword being boring) because in my line of work, interesting (usually) = bad.
What’re yours?
In inpatient psychiatry I tell my coworkers “I hope your shift is mind-numbingly boring” or something similar (keyword being boring) because in my line of work, interesting (usually) = bad.
What’re yours?
I hope your new code compiles with only a few errors.
If it compiles with tons of errors, it’s gonna take a while to fix, but if it compiles with no errors, that probably means it’s so fucked the compiler can’t even help. Every once in a while I’ll code something error-free first try, and it always takes more time because I’m trying to figure out if it’s actually error-free.
I like lots of errors because it usually means I did one major thing wrong and everything else works once I fix it.
Write some god damn unit tests before you write your functionality
I’ll embrace test driven development when I’m 6 feet under.
Based.
This is a really good example of the specific vibe I was going for. A good next question would be: “what is a good thing in your niche industry or hobby that most outsiders would consider a bad thing?”
That’s what unit tests are for