SOO TRUE!

CLASSIC: when there is a big emergency at the office everyone is going crazy and looking for you even under the rocks and you show up at the office 😎😏

Me: Hey let's do A to help the website.
PO: Yeah that sounds good. but let's do some research about it.
6 months later.
PO: Hay let's do A to help the website.
CTO/CEO/PO's boss: amazing idea. Here's an award and some money for that.
Me: What. The. F...

When you are a junior dev and you ask howto do some shit to a senior dev. He answers vaguely and you have to keep asking during the wholr process instead of getting a full answer from the beginning

Project life cycle for developers

Describe your stress level in one sentence.

I'll kick it off:

"If he sends me one more passive aggressive email, or moronic statement, I will hit him with my chair until he stops moving"

10 PM (after a very busy working day), CTO calls me and tells me: "We decided to hand in the new version to [random client] one week earlier, so they can test it."
Me: "I don't think is a good idea, the app is still unstable, we started working in it yesterday, it *will* crash"
CTO: "Don't you worry, at least they know we are working on it"
20 minutes later
CTO: "WTF why did you make my app crash?! I can't send this to a client!"

Told you. That is why that code is on develop and not on master.

I'm looking for the maximum -- one can attain from a single post. Please down vote this if you will.