Mason  🏃‍♂️ ✂️

Another layer: people think the problem is "taking the easy path." That's not the problem! The problem is not *fully defining any desires* that don't already have a well-trodden path to their satisfying condition, never allowing them enough weight to fall out of the cloudshttps://twitter.com/webdevMason/status/1006181402944028673 …

A lot of people seem to choose paths *instead of* destinations, so - they never really hash out exactly what they *want* - they’re liable to get caught in loops to nowhere - they might get frustrated with people who seem to be getting more with less (obvious/visible) work

Choosing a destination as a means of setting shorter term priorities is a bad idea. It makes it hard to discover your mistake until you're dead. Hash out what you want NOW—much rarer & harder than it sounds—and think about the long term as one of many ways of criticising that.

The way I'm thinking about these terms: > desire — what you think you want > destination — set of conditions that you think will satisfy your desires (many could be feasible) > path — the actions that you think will move you closer to your destination

I think you basically can't go wrong trying to understand your desires, as long as you also understand that they're not all necessarily stable & it's possible to be wrong about them. This is true of your destination & path, too, but there are additional risks there...