Doing a thing involves doing it, but it's very unlikely that doing a thing will involve exactly one atomic movement. So you have cutpoints at doing the thing.
So to do the thing you first have to decide to do the thing. You have to decide what the thing is, or at least have enough of a vision of the thing to take the first step at doing a thing that might look like the thing.
So "doing the thing" involves a lot of doing things that aren't the thing, but without which you won't get towards the thing.
In other words: sitting down and writing down what the thing is _can very well_ be part of doing the thing.
There's a sort of philosophical point too, about whether the thing is what you think it is. Plenty of people have had the "I thought this feature was going to do X, you thought it was going to do Y, and we all realised the mismatch very late in the process".
I think both visions of the world are valid, and things you can keep in your mind at the same time to deploy as needed.
Or you could try and learn by experience. Software is an example, but so could be drawing or composing music. All of those things have been taken to extreme highs by people who had no idea what they were doing.
Becoming someone who can do the thing is how you get to do a lot of things
Not what your boss and your bosses’ boss wants you to do, instead of doing other things you can do to maximize value for shareholders in some arbitrarily chosen amount of time
But thinking of how you wouldn’t have permission to get ready to do the thing in a business context, also, isn’t doing the thing
This hints at the antithesis to this article
Doing a thing involves doing it, but it's very unlikely that doing a thing will involve exactly one atomic movement. So you have cutpoints at doing the thing.
So to do the thing you first have to decide to do the thing. You have to decide what the thing is, or at least have enough of a vision of the thing to take the first step at doing a thing that might look like the thing.
So "doing the thing" involves a lot of doing things that aren't the thing, but without which you won't get towards the thing.
In other words: sitting down and writing down what the thing is _can very well_ be part of doing the thing.
There's a sort of philosophical point too, about whether the thing is what you think it is. Plenty of people have had the "I thought this feature was going to do X, you thought it was going to do Y, and we all realised the mismatch very late in the process".
I think both visions of the world are valid, and things you can keep in your mind at the same time to deploy as needed.
"Whoever does not know how to hit the nail on the head should be entreated not to hit the nail at all." -- Nietzsche
Or you could try and learn by experience. Software is an example, but so could be drawing or composing music. All of those things have been taken to extreme highs by people who had no idea what they were doing.
Naivety has its perks.
No, you’ll still need to do it.
Yes just do it without knowing how to do it! That always works out well.
In software, where the consequences for initial failure are extremely minimal, sometimes it does actually work well.
But learning about, while possibly a prerequisite, still isn’t getting it done.
The point is: don’t stop at learning how to do the thing.
Actually do the thing.
2 replies →
Then it isn't a thing you can do.
Becoming someone who can do the thing is how you get to do a lot of things
Not what your boss and your bosses’ boss wants you to do, instead of doing other things you can do to maximize value for shareholders in some arbitrarily chosen amount of time
But thinking of how you wouldn’t have permission to get ready to do the thing in a business context, also, isn’t doing the thing