here is also a link to a video interview of Jeff Bezos explaining that he prioritizes sleep, because at his level, quality of decisions is more important than quantity of decisions.
Read the critisim section. There is no reason to think hunter-gathers worked only 4 hours per week, unless you define work so narrowly that the majority of what they did doesn't count even though anyone who has done those tasks knows how much work they are.
What is work? Those religious services were mandatory to set the image of him as a king. The discussion around the jewels was also mandatory - again setting an image. While he had the ability to skip any of those things, not doing them sets him up as an image of a bad king and soon he will be removed.
If go had started out having different syntax for error handling, would these same people request that it change to what go currently does? Or is this just resistance to change, and wanting to keep what they are used to?
- It has poor visibility, it hides control flow branches in a single statement / expression. That's one of the reasons Go got rid of the ternary operator in favor of an if statement where each branch has to be on its own line.
- It isn't easily breakpointable.
- It favors "bubbling up" as-is over enriching or handling.
You set a breakpoint directly before this line, and then step forward. If you need the breakpoint to only trigger when there is an error, then you can use a conditional breakpoint that triggers when err != nil
