3 ms·
One thing I used to do was to badmouth my own code to my team during our team code review/chat sessions. It usually went that we would pick a problematic sectio
by manyxcxi 10y ago
One thing I used to do was to badmouth my own code to my team during our team code review/chat sessions. It usually went that we would pick a problematic section of code from some project, we'd talk about an elegant snippet of code we came across (from any project we came across), and some interesting new things.
During the problematic code section if I was harsh they usually knew it was my name they were about to see in a commit log. It was a dramatic effect to prove the point: even the people who are supposed to be championing quality have a bad moment for whatever reason, no one is safe from shitty code or bad ideas and executions, and anyone can write something elegant and sneaky awesome. One bad commit doesn't make a shitty engineer, so don't go calling everyone else's code garbage. If you're really as good as you think you are you can fix it.