When programming, I tend to be a typical flow which roughly goes: problem definition → thinking → typing. This is a summary of how I approach problems, with a catchy title I’ve gone with “What if? driven development”. The five whys The five whys is a technique for discovering the root problem, from some symptoms. Simply put: given a problem, if you ask the reporter why five times, you will discover the root of the issue.
What if? driven development
What if? driven development
What if? driven development
When programming, I tend to be a typical flow which roughly goes: problem definition → thinking → typing. This is a summary of how I approach problems, with a catchy title I’ve gone with “What if? driven development”. The five whys The five whys is a technique for discovering the root problem, from some symptoms. Simply put: given a problem, if you ask the reporter why five times, you will discover the root of the issue.