I was about to implement a new feature (which I will call feature X), but I was not sure which branch feature X should be implemented on. Because of different products, there are a lot og branches around.

I was going to implement feature X on branch A, but that branch was currently not working, and someone was working on fixing it.

I was told by my boss to branch out from branch B as feature X would be merged in there later anyways.
And so I did.

After I am nearly finished with feature X I discover I need feature Y from branch A. Feature Y is not yet on branch B, but is scheduled to be merged in some time soon.

So I can't really finish feature X before that point, and I am told by colleague 1 I should have implemented feature X on branch C, because feature Y is there and branch C will be merged into branch B soon.

However, I found out that this has happened before.

First, colleague 1 was told to implement feature Y on branch A. This is the real implementation, the one I need. After he had spent a week implementing feature Y, he was told by colleague 2 that the feature should be implemented on branch C, which is branched off from branch B (I think). So he had to spend a day or two to move feature Y to branch C, but he still kept feature Y on branch A, because all branches will eventually be merged into branch A.

After a week or so, colleague 3 asks about feature Y and is told that the feature is on branch C. But colleague 3 need the feature on branch D, which is branched off branch B for some weeks ago.

I don't know all the details here, but colleague 3 ends up implementing a version of feature Y on branch D and he is happy.

I don't know how much time was wasted because of wrong information from management, but I have no intentions of wasting more time. I'll wait for the merge of branch C into branch B.

If this rant makes no sense, that's just my reflection of management some times.

I love management.

When you have just made a new feature and you rebase to master, and the project won't compile because someone else pushed something which doesn't work...

I just found out that I am my co-workers rubber duck...

Shit! I've been so focused on my work today that I forgot to check devRant, and it's soon 2pm!
How have I survived...?

My boss: "We need this feature by Friday"
Me: "I can make it work, but I need more time to do it properly"
Boss: "Just fix it by Friday, and you can make a proper implementation later, when there is time"

Like there will ever be time once it works...

Debugging overcomplicated code I didn't write is like debugging black magic.

My estimations before devRant:
PM: how long will it take to implement this?
Me: one day, tops.

My estimations after devRant:
PM: how long will it take to implement this?
Me: one week, tops.

Thanks @dfox for making me so productive.

It would make sense to me if the number of ++ you need to get a stressball increased by one each time someone earned it.

One year ago I graduated from university college,
Thought I had a stack overflowing with knowledge.
How wrong can one man be?
Very wrong, apparently...
Even though I only had a bachelor degree,
I landed a job at a nearby company.

Today I'm maintaining the code I wrote back then,
Seriously wondering if I could just write it all again.
The code I wrote I would consider a crime,
But it's good to see improvement over such a short time.
I still dread coming back to this code in another year,
Thinking yet again; "What the hell went wrong here?".

I used to go through my Google Now cards each morning while eating breakfast.

Google Now has been replaced by DevRant.

I'm staring into my empty coffee mug,
hoping I could find this annoying bug.
Like always I have no such luck,
so I'm turning to my rubber duck.
He's emotionless expression I cannot read,
Guess he doesn't have what I need...
I can feel the bug mocking my face,
While I'm aimlessly looking into space.