|
|
|
|
|
by 1penny42cents
1994 days ago
|
|
OP is giving a problem solving framework, it's not tied to specific solutions or tradeoffs. It's more of a method for thinking through a solution. In more detail, the steps go like this. Find as many solutions to a given problem as you can. Bad engineers run with the first solution that comes to mind, letting confirmation bias drive them. Evaluate each solution for its costs and benefits. Imagine two steps in the future when the solution is implemented. What pains are there? Search for creative new solutions that create win-win scenarios. That's riding the solution curve. Given all viable scenarios, compare the costs and benefits against the quality measures for your specific context. Some projects value speed over precision. Some projects value performance over extensibility. Some solutions are easier to change later than others. This is choosing a specific point on the solution curve that best fits your context. You can apply that method of problem solving to any problem, large or small. You don't need a ton of experience to practice it. |
|
I’ve repeated it that exercise with junior engineers to great effect. Some catch on over time and start intuitively considering the trade offs of a few reasonable solutions to a problem; some don’t.
I never reflected on what he was doing there; thanks.