I am amazed how developers avoid to write CSS at all costs! They prefer to struggle with a CSS library than write simple CSS rules.

But the truth is that you cannot even use properly these libraries if you just don't want to understand CSS.

In the end, the result will still look horrible with an extra dependency on the list

Had another meeting today. The solution architect said two insulting jokes about developers like:

"The devs will nevertheless mess it up"

Devs are the ones who make chaos

This meeting was with a customer and his developer. I was just furious!

This useless son of a bitch needs to learn his lesson

"we need to reduce the amount of meetings" said the super-duper senior enterprise manager who invited me to 20 meetings for the next 2 weeks.

To be honest, I haven't figured out yet what he is actually doing 💅

Don't reinvent the wheel! Use at least Apache commons in your Java app

Day 1. Push branch. Make pull request😀
Day 5. Got reply to fix some silly stuff🤡
Day 6. Apply changes. Ask for review again.😊
Day 7. Needed to work for another project for two weeks🤝
Day 25. Came back and pull request and branch were deleted from server 🧐🧐
Day 26. I merge my local branch copy into master and push it to server. So long bitches! 💅💅

Ticket waiting for code review for days. I have to rename methods.

Tickets goes again to code review. Waiting there again for days. Oops! there is something the code reviewer didn't see before!

Ticket goes to code review again, waiting for days there.

Boss comes to me telling it takes me too long to close tickets.

Code reviewer tried as hard as possible to find issues in my commits.

After timereportimg 3 hours extra in a small ticket, he concluded we needed to try a different approach, even if code was OK? Why?

Simply because it was his idea and his idea is better. The reviewer needs to feel his superiority by any means.

Hmm. Seniors have the half working experience as I do and I am the only not senior one in Dev team.

I adapt code only to "taste" good for code reviewers, but they allow themselves to commit without caring and just saying :"oh unit testing is boring"

Enough with the kindergarten. Time to prepare myself for the next job.

In code reviews they are whining about formatting with spaces and newlines and naming.

The fact that they are too bored to write unit tests and code coverage cannot reach 20%? Isn't it just sad?

(colleague) Are you still using Emacs?? why don't you use Sublime instead?
(me) Because I am a PERVERT and I god damn LIKE it (being pervert & Emacs)

I hate it when implementation takes less time than business analysis. If you cannot refine requirements after years of discussions, make Earth a favour and shoot yourselves. Do not force me to implement something that you will probably never use.

UI web developers tend to change frameworks more often than underwear: almost every month

i am switching jobs like a monkey switches trees. I never leave a branch before I grab the other one.