Haven’t come across this before but I can see myself using this framework of how, what and why in the future. Few thoughts… How: Talking as a mid level progra

Haven’t come across this before but I can see myself using this framework of how, what and why in the future. Few thoughts… How: Talking as a mid level programmer, I can’t control the language of choice, I can’t influence the framework or the design. I can control how the individual piece of algorithm is written. What: Apart from the function names, the main important thing here is abstraction. Abstraction is a long term game and it improves with your understanding. The abstraction you choose with a few weeks of exposure to the domain will be entirely different when compared to the person who knows the domain for 10 years. Your abstractions can also changes with the exposure to the actual problem in hand. The more you go down the rabbit hole the more abstraction will keep changing. I like what Kent says here… https://kentcdodds.com/blog/aha-programming https://kentcdodds.com/blog/aha-programming As the author says, it takes years to develop the overall taste but also it takes time to find the right abstraction for solving the problem in the domain. Why: Never thought of comments as the why. I used to think of comments as what more than why. Simple but important distinction. Thanks for the insights.