Live data from Hacker News

Slow is smooth, smooth is fast: Navy SEALs' efficiency secret

navyseal.com

31–40 of 163 posts

Re: Slow is smooth, smooth is fast: Navy SEALs' efficiency secret

#31

"Pants on fire" startups would do well to learn from this... a whole lot less stress and better results vs. slamming out midnight patches.

Sometimes urgency does matter; for example, when I ran Tinfoil, we got a lot of good press from being the first ones to release a public vulnerability checker for things like Heartbleed and so on, and it was a common reason we made sales. Getting those out within 12-24h was an intentional part of our model, because our competition would take a week, so it was trivial to make them look bad.

That said, it was extremely important for it to be correct, so we never cut corners. Best way to never make a sale is to tell someone they are patched when they’re not.

But speed can be a major factor sometimes. It just can’t be the only factor.

Re: Slow is smooth, smooth is fast: Navy SEALs' efficiency secret

#32
post #26

I've been taking glassblowing classes for a few years, and this is easily the biggest lesson there. If I rush something, I will fuck it up. If I let things happen bit by bit while they can go smoothly, everything comes out much easier. This probably applies everywhere, but it's really stark when you're playing with quickly-solidifying goopy liquid sand

> but it's really stark when you're playing with quickly-solidifying goopy liquid sand

I already wanted to learn glassblowing, but hearing it described this way just sold me on it completely. I’m gonna go find a place. :)

Re: Slow is smooth, smooth is fast: Navy SEALs' efficiency secret

#35
I've only heard this in the context of Smash Melee, which has limited-to-no input buffering.

If you try to input your attacks and movements too soon, they won't come out at all. So advice to new players is to err on the side of being slow, since it ensures the move input gets registered.

Re: Slow is smooth, smooth is fast: Navy SEALs' efficiency secret

#37

Have long stood by this belief and still do but modern IT calls it legacy and antiquated. Oh how we've lost The Plot.

The modern attitude is discard everything "old", not immediately understood, and abandon standardization and simplicity.

Eh, I don’t think that’s true. I think you’ve just had bad experiences, and that that can definitely be true in pockets.

For example, I am exceptionally happy that we have standardized on OpenAPI documentation and/or the self-documenting nature of GraphQL (where used) rather than WSDLs and the other ancient nonsense.

I’m also glad we’ve mostly progressed from SAML to OAuth2/OIDC/JWT. Sure, SAML still exists but it’s definitely on its way out, once the enterprises of yesteryear eventually switch.

I don’t know if you’ve ever built a SAML application and/or IdP, but it’s awful.

Sometimes “old” is just worse.

Re: Slow is smooth, smooth is fast: Navy SEALs' efficiency secret

#38
In mechanics this is similar to 'kinematic efficiency'. The idea is to achieve smooth and efficient motion by optimizing the ratio of useful work output to total energy input, without caring fo the forces that initiated the motion.

In other words, focus on making strategic decisions and making sure you are aiming in the right direction rather than pumping your chest when you pull an all-nighter or feeling too proud about "staying busy". No one cares!

Re: Slow is smooth, smooth is fast: Navy SEALs' efficiency secret

#39
Sounds like 'kinematic efficiency'. The idea is to achieve smooth and efficient motion by optimizing the ratio of useful work output to total energy input, without caring fo the forces that initiated the motion.

In other words, focus on making strategic decisions and making sure you are aiming in the right direction rather than pumping your chest when you pull an all-nighter or feeling too proud about "staying busy". No one cares!

Post reply on HN