The windows/microsoft fanboy I've ranted about multiple times.

- wouldn't use anything except for windows. Even if required for a project (I would if really needed, have done that a few times already)
- refused to use any framework/language not written by Microsoft
- tried to get other projects to use windows/.net when it wasn't required and it was only linux/php guys (and that fit the projects perfectly)
- ONLY wanted to use Skype and whatsapp. Always bragged about how he had 10gb of Skype history.
- didn't want to use anything related to linus torvalds or open source because 'those are open source and have no business model so they're bad'

And then: he suggested the use of windows server right after one was hacked (windows vuln that wasn't patched yet) which caused the devops guys to want to install a new Linux server for it.
Even the windows sysadmin pointed to the door when he said that and gave him a huge 'GTFO' face cD

Yeah, fuck him.

I swear the the majority of my work is spent on "how can a user fuck this up"

It's never a "5 minute fix".

A rare bug appeared. It was my duty to finish it.

SH = Manager

SH: So when do you think you can finish the task?
Me: I still have to analyze the problem. Give me a moment and I'll get back to you.
SH: Alright.

*An hour later*

SH: *Approaches my desk* Have you found the source of the problem?
Me: Not yet. Please give me some more time.
SH: Ok.

*An hour later*

SH: *the approach* You found it yet?
Me: Yes, I've found the the source of the problem, But... *explains the problem and thus concluding that it's a complicated bug*
SH: Can you finish it by tomorrow?
Me: I'll do the best I can but I am not entirely sure if I can finish it by tomorrow.
SH: OK great!

*The next day*

SH: *Le approach* Hey I have a colleague here that may be able to solve the problem, he has skills with XYZ. Ok, I will leave you two at it then. *the leave*
Helper: So can you tell me about the issue here?
Me: *explains the bug and the source of the problem*
Helper: Have you tried solution A?
Me: Yes sir, but it yields a different output... *explains what happened with solution A*
Helper: Well, that won't work. What about solution B?
Me: I've tried that, too. *Another lengthy explanation*
Helper: Welp, ok. I'll get back to you on that.

(...But he never came.)

*A few hours later*

SH: *A.P.P.R.O.A.C.H.* Hey I have this team lead from another department. I think he can help you out on this one. *L.E.A.V.E.*
Helper 2: What seems to be the problem?
Me: *Explains again with all the solutions I tried but failed*
Helper 2: Wow. That really seems to be a complicated problem.
~~
Me (In my head): -_-
~~
Helper 2: Listen, I need to get back to my team. I'll keep you posted if I happen to find a solution for your problem alright?
Me: Alright thanks.

*Towards the end of the day*

SH: *APPROACHHHH* Have you resolved the bug yet?
~~
Me (In my head): You made me spend half the FUCKING day explaining to these people who didn't even give a piece of FUCKING SHIT to contribute to the problem and you are asking me if I am done with this FUCKING BUG? FUCK YOU, YOU SON OF A -
~~
Me: No, it is not finished yet..
SH: You have to finish this because we don't have tomorrow.
~~
Me (In my head): SHDIFHWISGSIFGSISBAUDBEIQBDIWGFIEBWIDHWIQBDOSBCISBDOSHDIAGSUSVDIFBDKDJWIQKDBDIDGSUWVDIABDIXBSIDBDIDBWUWGUSVDUWVDJQBDUDVWISHDUWVFG
~~

I went home for the day.

I was in school and I got bored. I opened two command prompts and did what any scammer would do.

I went to the root of the drive and did a tree. The other window is pinging google infinitely.

After a few seconds, I hear a kid say "Are you hacking the pentagon?". That guy also asked me to hack the Google Play Store. He shall forever think I'm a hacker.

Not separating different changes into different commits, and just adding "a few tweaks" when I can't be bothered to list changes.

git commit -m "Added x, updated y, renamed z, and a few other tweaks"

I'm so sorry if this has been posted before! I thought it was kinda funny, and ought to share it with you guys.

Pet-peeve: fellow devs who think scoffing/dismissing/not-my-probleming before actually understanding the issue is a sign of intelligence; newsflash: you are being lazy, disagreeable and unprofessional.

In response to the picture I posted of my boss's wiring, we got a new switch today and he cleaned it up a bit.

When I was studying OOP our teacher instructed us to submit a project at the end of semester. Me and my friend worked hard and enthusiastically and finished our first game in C++ (Ping Pong). We were very excited because we had put so much effort into it that we were 100% sure that our project will be the best among all. At the end of semester, turned out our teacher does not have much time to evaluate our projects, so instead he announced a motherfucking MCQ's quiz. Everyone got really really happy but I was thinking of multiple ways I could kill that bastard.

Management is wondering why development and IT are taking the day off.

Happy Switch Day!

Some words of wisdom passed on by our Scrum.

1. I am responsible for setting boundaries. Work time, sleep time, family time, me time. If I don't set them properly, things WILL get unbalanced very quickly. (And I would add, burnout will follow closely).

2. Being productive isn't about doing more and more in less time. It's about doing only the most important things well, and either saying no to the other things, or finding another way to get them done. (Prioritize!)

3. I can't win (let alone run) a marathon by thinking of it as a 26 mile long sprint, or a week as a five day sprint. (Eat a digital elephant a byte at a time).

4. Loved ones are good judges of when things are in and out of balance.

5. Taking time off is essential. Vacations, yes, but also nights and weekends. (Or you WILL burn out and hate what you do).

Comments in () are mine.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!