In this lesson we discuss how Boris came up with so many impactful side projects. We also look at how automation became one of his main sources of leverage.
- He kept a spreadsheet of repeated code review comments and wrote a lint rule whenever the same issue came up more than a few times, until most of his reviews were automated.
- Better engineering projects fit the performance review criteria, so he offered them as opportunities instead of telling people what to do, and one example was a way to unit test very large data sets.
- His rule of thumb is that if you hit the same problem two or three times, check whether others hit it too, and build for yourself first because that’s a good sign others share the problem.
Original podcast link: https://www.youtube.com/watch?v=AmdLVWMdjOk