If you identify with these, chances are you’re a developer.
1. When coding all night without coffee makes you “sabaw”.
2. You still don’t know how debugging actually works.
6 stages of debugging
1 That can’t happen
2 It works my machine
3 It shouldn’t happen
4 Why does this happen?
6 How did it ever work?
— Mike Sax (@mikesax) March 5, 2014
3. Having to explain this to your non-programmer friends never gets easier.
“So this SEO copywriter walks into a bar, grill, pub, public house, Irish bar, bartender, drinks, beer, wine, liquor” — L.A. Weekly (@LAWeekly) January 10, 2011
4. When you start losing grasp on the English lang10100111001010101010101001001001…
5. When you end up explaining to a non-programmer friend why you believe “the root is actually at the top of the tree.”
6. When you ‘genuinely’ understand why COBOL programmers know why women hate “periods”.
7. When you finally believe salsa’s not always fun.
Chunky Salsa: A single critical error or bug that renders an entire system unusable, especially in a production environment.
8. When you know codes smell, too.
Code Smell: Any symptom in the source code of a program that possibly indicates a deeper problem. Code smells are usually not bugs—they are not technically incorrect and do not currently prevent the program from functioning. Instead, they indicate weaknesses in design that may be slowing down development or increasing the risk of bugs or failures in the future.
9. Or you spend months building an app, and the App Store ends up rejecting it.
10. And when you get to meet people who believe all programmers are fat.
Note: This is for fun only, peeps.
All GIFs grabbed from Giphy.com.