Re:Evil programmer's tip: avoid “easy” things (2016)
by ravenstine on Wednesday July 28, 2021 @08:50PM
(#27991535)
Reminds me of moments I had early in my career where I was the hero for fixing problems I caused. :) That company didn't have code reviews and my bosses weren't very technical, so it was pretty easy to pretend like I wasn't at fault for anything. Sometimes they'd figure out that I caused the problems and even then it didn't seem to really matter. If I had the skills I have now 7 years later, my bosses would probably think they're overpaying me because it wouldn't seem to them like I'm doing anything more of the time.
[ Parent
| on HN ]
Re:Evil programmer's tip: avoid “easy” things (2016)
by toast0 on Wednesday July 28, 2021 @09:01PM
(#27991609)
If you don't get enough praise for not breaking things, get a days since a workplace accident sign, and update it every day.
Set it to zero when you break something.
Edit to add: you should be able to get some praise (or at least self-praise) at milestones like 30/60/90/180/365 days without an incident.
Re:Evil programmer's tip: avoid “easy” things (2016)
by dreadlordbone on Thursday July 29, 2021 @12:04AM
(#27992669)
Recently one of my clients noticed something we had broken on their website. When they noticed it, we fixed it in a matter of minutes. They were so pumped on the response time they then left us a very glowing public review.