News for hackers. Stuff that matters.
Re:A Senior Engineer's Check-List by Nevermark on Sunday September 10, 2023 @03:32PM (#37459137)
An important skill would be:

1. Identifying every project dimension with risks. The big one: project -> use -> user -> reward -> costumer fit? (Where user and customer may, or may not be the same.)

Price cost economics complexity? Technical experience shortfalls? Project resource availability? Solution resource efficiency? Safety? Third party dependencies?

2. Identify each significant risk in each risk dimension.

3. Identifying the simplest question (or two) whose answer will reduce or eliminate each risk.

4. If a risk can’t be mitigated by answering a single question (or two), maybe it is really a combination of risks, or risk dimensions. If so break the out, repeat.

4. Crafting the simplest research task to resolve each risk question.

This approach is special case of solve hard upstream tasks, before investing downstream tasks, as efficiently as possible.

Or as I like to say: move slow to move fast.

A meta risk is that solving some risks might require working downstream from some unresolved risks.

Getting buy in from particular stakeholders, by building something far down the risk stream, before a up stream risk is resolved, is a classic chicken & egg problem.

At least identify those loops in risk dependency so the lowest risk, highest efficiency path can be taken.

There are no comments on this comment yet.