←back to thread

Focus on decisions, not tasks

(technicalwriting.dev)
293 points kaycebasques | 1 comments | | HN request time: 0.204s | source
Show context
ChrisMarshallNY ◴[] No.41883501[source]
This is what I generally mean by taking an "heuristic approach."

I feel that we need to have a "fuzzy logic" approach to our work.

However, that works best, when the engineer is somewhat experienced.

If they are inexperienced (even if very skilled and intelligent), we need to be a lot more dictatorial.

replies(2): >>41883516 #>>41883959 #
Swizec ◴[] No.41883516[source]
Thinking in Bets has been one of the most useful books to how I approach software engineering. It’s not even about code, just how to make decisions effectively in limited information environments.
replies(1): >>41883593 #
kaycebasques ◴[] No.41883593[source]
Love that book. Such a powerful idea to phrase your predictions in terms of percentages rather than absolutes. Apparently the Super Bowl anecdote is controversial though? I.e. the conclusions to draw from that anecdote are very debatable.
replies(1): >>41883677 #
1. Swizec ◴[] No.41883677[source]
I don’t remember the specific anecdotes too much, but the lessons make intuitive sense and feel useful.

The one that sticks to mind most is that a good decision can have a bad outcome and that a good outcome doesn’t always mean the decision was good.