In one of the latest articles on Farnam Street Blog, I learnt about the concept of second-order thinking and Chesterton’s Fence heuristic. As a result, it made me think of one of the very common behavioural patterns in tech – you join the company when something is already built, you don’t see value in it, or you believe that it could have been done better, and you start either to remove, either to refactor services or architecture. What can go wrong here and how is it related to decisions documentation? Chesterton’s Fence When we don’t agree with what we see, we use to think that someone did it without knowledge…
-
-
The art of code review
I heard in a podcast position of one lead developer about code review. He stated that he doesn’t see much sense of doing PR review after 3-4 times since a new person joining the team. Reasoning was that if they hire a developer, they assume that these number of PRs with comments will be enough for this person to understand the code style and standards of the team. And after that code review is not valuable anymore. Every team decides what better works for them, but my experience shows that code review is not about telling others how to properly write this or that line of code, and to hope…