- fully specify the problem before jumping in. Write what you know, the context and the unknowns.
- Write the steps of the solution before jumping into a problem.
- If writing a report, create the outline/heading structure before doing any other writing.
- If you want to do something non-trivial, quickly search the web to see if someone has written a library or has a one-liner to save you time.
- 80% of your results will come from the first 20% of the total time you spend working on something. Anything after that is polish. This helped me to overcome perfectionism.
- If you don’t know something, ask a colleague or peer. They will be thankful for the opportunity to teach you something.
- If you’re ‘stuck’ on something, completely switch context for an hour or even a day. The subconscious mind does serious heavy lifting, it just needs time (and rest!).
- if you’re learning a new concept and struggling, don’t write detailed notes straight away. Your notes at this stage reflect a naïve understanding. Letting an idea ‘ferment’ before writing about it will result in primo notes.
- Don’t spend too much time buggering around with tools and tech. If you’re spending more than 30% of the total task time on ‘ceremony’ or ‘config’, it’s a hindrance.
There’s more but these are the main ones.
I just didn't expect it to keep popping up in a technology focussed community. Yet I can see the appeal. The sheer determination of Shackelton and crew should be inspiring to all people.
A memorable element was the mens’ reaction to WW1. Them asking “who won?” felt awfully like one would ask about a football game.
But I found Ernest endlessly describing every depth measurement and the stomach contents of every penguin they killed hard to get through.
SPOILER ALERT
1) Where they are navigating broken ice on a heaving ocean and Shackelton casually mentions that he hadn't slept for over 100 hours as he was trying to pick a safe route through the ice (I expect people would argue that is highly likely to kill/drive you insane).
2) Where a wave breaks on top of their small boat that is so high that they can't hear it yet and Shackelton initially thinks the white crest way above them is actually a break in the sky indicating clearing weather.
And I have a sore neck because my keyboard/monitor arrangement isn't optimized.
I live in the flatlands near some mountains. I can look at one of the websites that show data from personal weather stations to see that the temperature is 15 degrees cooler up on the mountains. But windy shows the temp there being the same as here. I figure it’s just averaging the various locations around (but not on) the mountains. Better data exists, but they don’t seem to have it.
Turns out being very specifically wrong is more convincing than just being generally wrong.
EDIT: I should add that windy may be the best forecasting app there is. I was more commenting on the fact that the specificity made me follow it blindly when I should have been treating it like any other forecast.
Maybe thats unfair and just "let the people decide" is the best method but 'wow!' am running adblock and that thing is still a sensory overload.