[adsense_leaderboard]
1. You become the computer repair guy.
Truth: Most of the time you just Google the problem.
2. You suddenly forget how to code because… Stack Overflow is down.
Stack Overflow is now experiencing a DDoS attack. We are working to mitigate.
— StackExchange Status (@StackStatus) May 6, 2015
@StackStatus can you please Stack Overflow to fix Stack Overflow? I’ve no idea what I’m doing right now. [adsense_center]
3. When you change one line of code.
4. When you try to solve a bug.
5. When someone interrupts you.
This is why you shouldn't interrupt a programmer: http://t.co/K2dNXKzjem
— Jason Heeris (@detly) October 28, 2013
6. Or maybe no one interrupts you, but you want to pee…
7. End user have no idea how to use your software.
[adsense_center]
8. Critical issue… cannot reproduce.
9. JavaScript.
Sometimes when I’m writing Javascript I want to throw up my hands and say “this is bullshit!” but I can never remember what “this” refers to — Ben Halpern (@bhalp1) March 20, 2015
10. When your manager thought more developer means faster development.
11. More tasks on Friday afternoon.
12. Hey can you please add a button before it goes live?
I mean, it shouldn’t take too long right?
13. CSS in a nutshell.
14. This code looks like crap, let me refactor it.
15. When you try to fix something else’s code.
Congratulations, it’s now your problem!
16. Everyone thought you are a hacker.
Hey can you help me to hack John’s Facebook?
17. When you read other people’s code.
18. When you are given 2 days instead of 3. Because you don’t have leadership skills.
19. This sums up programming.
It’s OK developers. At the end of the day software developer is still one of the best jobs in the world!
If you like this, you should check out 21 things that only developers will understand.
Share this to your programmer friends by clicking below!
