blog series: Problem Solving #42

New Issue

jeff · 2022-01-14T20:00:59Z

jeff commented

2022-01-14 20:00:59 +00:00

Defining the problem
Testable: define the problem you're solving, and check it once it's done.
Knowing when to stop
Check that you are not investing too much time for a given problem. Step back and take a break.
Getting something to work in stages. Don't prematurely optimize. Start with hardcoded values. Working solution before best solution.
The best solutions are more complex to understand. It is therefore useful to test against simple ones, which should be created first.
Break into stages (persistent pipeline)
Ex: Store data as it comes in, then store a cleaned copy. This gives repeatability and repair.
Plan of attack
This is the cheapest, most efficient, and most effective time to solve a problem. Changing course is essentially free.
Document the finished product before it is finished.

1. Defining the problem Testable: define the problem you're solving, and check it once it's done. 2. Knowing when to stop Check that you are not investing too much time for a given problem. Step back and take a break. 3. Getting something to work in stages. Don't prematurely optimize. Start with hardcoded values. Working solution before best solution. The best solutions are more complex to understand. It is therefore useful to test against simple ones, which should be created first. 4. Break into stages (persistent pipeline) Ex: Store data as it comes in, then store a cleaned copy. This gives repeatability and repair. 5. Plan of attack This is the cheapest, most efficient, and most effective time to solve a problem. Changing course is essentially free. Document the finished product before it is finished.

Sign in to join this conversation.