11–20 of 177 posts
"when you punch someone you need to pull your arm back, before you launch it forward. If you don’t your hit will be weak." It's a cute way to think in opposites, but unfortunately as punching advice, it's untrue. Punch force comes from body mass x acceleration, not arm mass x acceleration.
Efficiency is also more important than it seems. You can have lots of low quality, half-baked output. How much forethought do we put into what we will work on to begin with? Some projects and ideas are not worth the effort. Or an alternative solution to a problem is preferable over one you’ve been hammering away at for days, and would be easier to implement. And in the realm of programming, it’s often easy to take sh…
Not every product is maintained for years. In many cases it's good to be able to choose between a quick solution and a good solution, as long as these are concious decisions and some record of accrued technical debt is kept.
At least according to my experience and everyone I know in the industry.
"when you punch someone you need to pull your arm back, before you launch it forward. If you don’t your hit will be weak." It's a cute way to think in opposites, but unfortunately as punching advice, it's untrue. Punch force comes from body mass x acceleration, not arm mass x acceleration.
Bruce Lee taught a martial arts technique that relied on not pulling back first - https://en.wikipedia.org/wiki/One-inch_punch
And I thought they wanted argue for faster replies...
But I think there is some truth to that. If a task seems overwhelming, it can sometimes help to look back at something you already completed.
I don't have that impression for programming at work, since I have a set schedule anyway, but for projects outside of that the kick-off seems to be the hardest part in awe of all the work before you. But then there is all the projects you already completed, which were mostly labor intensive as well.
Efficiency is also more important than it seems. You can have lots of low quality, half-baked output. How much forethought do we put into what we will work on to begin with? Some projects and ideas are not worth the effort. Or an alternative solution to a problem is preferable over one you’ve been hammering away at for days, and would be easier to implement. And in the realm of programming, it’s often easy to take sh…
"when you punch someone you need to pull your arm back, before you launch it forward. If you don’t your hit will be weak." It's a cute way to think in opposites, but unfortunately as punching advice, it's untrue. Punch force comes from body mass x acceleration, not arm mass x acceleration.
Oh please. Our whole product is a side effect of "working quickly", and it's anyone's guess how difficult it is to make any change in that now.