5 ms·

At the highest level, it's difficult to argue that anything actually matters. So being in a hurry is as pointless as pondering endlessly to make the best choic

At the highest level, it's difficult to argue that anything actually matters. So being in a hurry is as pointless as pondering endlessly to make the best choice. But since we create our own isolated realities, most of which are human-lifetime based, we tend to care about the passage of hours or days. And in that scope, sometimes being quick seems important, but also having perspective and time for reflection can. There is a time (pardon the pun) for blitz chess, and there's a time for clockless chess. What matters actually is the experience, not the outcome. If we believe that our approach resulted in a better outcome, we are happier.

bob1029 3y ago
If we are looking at this from a business perspective (which might map), the actual wizardry is in knowing exactly when to push and when to sleep on something. I think we can all agree that there are things you should think very deeply about before you even touch your computer or join the conference call. Things like what sorts of vendors and business partners you want to get married to for the next half-decade. If you want to be a Microsoft shop or some OSS champion (both valid in my view!). These kinds of things often times require starting a new company to fix after you commit. In our domain - the thing you don't want to spend a lot of time worrying about is the entire scope of the actual code/development work. Assuming you are using source control, you have a superpower that allows instant teleportation to any moment in time. The consequences of making a bad choice and acting quickly are negligible, assuming you aren't trying to lose the game on purpose (e.g. master builds straight to prod on unprotected pushes). It only gets to be adverse if you are unable to separate the bad from good ideas afterwards. Not reflecting on your prior works. I believe we'd refer to this as the "technical debt". I think it was Amazon that does the one-way/two-way door decision test. This is a fair criteria for deciding when to sleep on a proposal or when to shoot and then aim.
pazimzadeh 3y ago
> it's difficult to argue that anything actually matters > being in a hurry is as pointless as pondering endlessly to make the best choice Only during times of abundance (very recently). Historically, survival would be thing that mattered, and time is very important for running away from things, finding antidotes to poisons/disease, social coordination etc..
polynomial 3y ago
> There is a time for blitz chess, and there's a time for clockless chess. Arguably, there is more time for blitz chess.
pperi11 3y ago
Agreed - the rate at which we're consuming info as humans (FAST) is just harmful. Feels like it's deteriorating our bodies

bob1029 3y ago

If we are looking at this from a business perspective (which might map), the actual wizardry is in knowing exactly when to push and when to sleep on something. I think we can all agree that there are things you should think very deeply about before you even touch your computer or join the conference call. Things like what sorts of vendors and business partners you want to get married to for the next half-decade. If you want to be a Microsoft shop or some OSS champion (both valid in my view!). These kinds of things often times require starting a new company to fix after you commit. In our domain - the thing you don't want to spend a lot of time worrying about is the entire scope of the actual code/development work. Assuming you are using source control, you have a superpower that allows instant teleportation to any moment in time. The consequences of making a bad choice and acting quickly are negligible, assuming you aren't trying to lose the game on purpose (e.g. master builds straight to prod on unprotected pushes). It only gets to be adverse if you are unable to separate the bad from good ideas afterwards. Not reflecting on your prior works. I believe we'd refer to this as the "technical debt". I think it was Amazon that does the one-way/two-way door decision test. This is a fair criteria for deciding when to sleep on a proposal or when to shoot and then aim.

pazimzadeh 3y ago

> it's difficult to argue that anything actually matters > being in a hurry is as pointless as pondering endlessly to make the best choice Only during times of abundance (very recently). Historically, survival would be thing that mattered, and time is very important for running away from things, finding antidotes to poisons/disease, social coordination etc..

polynomial 3y ago

> There is a time for blitz chess, and there's a time for clockless chess. Arguably, there is more time for blitz chess.

pperi11 3y ago

Agreed - the rate at which we're consuming info as humans (FAST) is just harmful. Feels like it's deteriorating our bodies