AboutA mad burger living in Germany. Queer, gym rat, coffee junkie, against Politicians, Priests and Police. Hate fashion and expensive useless stuff.
Joined devRant on 4/3/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
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.1
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.1
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?7
(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)2
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.
i am switching jobs like a monkey switches trees. I never leave a branch before I grab the other one.1