45

Screaming at a coworker?
The INTJ in me has prevented that pretty well in almost every critical devSituation.
BUT one time in the past, I was really close to a level 9001 scream:
This fucker, despite having been told about code formatting guidelines and DRY/KISS multiple times, had the balls to commit such utterly crappy and unreadable code that I almost bursted.
He quickly realized his mistake after I reset the repo to before his push, disabled his Gitlab account and wrote him a simple email containing the text:
"IF YOU EVER COMMIT SUCH SHIT AGAIN, THERE WILL BE UNFORESEEN CONSEQUENCES. GFYS."
After a peaceful coffee and a croissant I decided to re-enable his account. He did good after that.

Comments
  • 7
    LMAO 😂
    Are there no code reviews before delivering changes?
  • 2
    @irene We're only 3 devs, so currently not...
  • 2
    @PonySlaystation my subteam has 4 devs and a lead. We always do reviews 🙃
  • 1
    @irene cool!
    I talked with my boss about this some time ago, but he was against it because our projects are mostly developed by one dev, rarely 2-3 and it would add more overhead to our current state. But I think we will soon start having code reviews, because more devs will join and I personally still think that it is needed. Code quality of my boss has not been great and an intern has joined us recently, so reviews are definitely needed.
  • 0
    @PonySlaystation well, I work at a corp and that is the demand from the customer. So we really have no choice. However it is very useful so I would do reviews voluntarily anyway.
Your Job Suck?
Get a Better Job
Add Comment