[unfocused828]

> Don't worry about it

As an engineer who has been fired twice for performance problems, I don't have that luxury.

> Break touch tasks down into very, very laughably small tasks.

This works well if you've used the technology/tool before and you feel like you understand what you are doing. It is very difficult if you are in the circumstance of having to learn things as you go and having to prodding at things and trying things to figure out how things work. In cases like these, it is better to just figure out what the smallest first step is and iterate that way.

Unless of course you have the breathing room to spend time working through a tutorial on whatever set of abstractions you are trying to work with.

[mryan]

> It is very difficult if you are in the circumstance of having to learn things as you go and having to prodding at things and trying things to figure out how things work.

With respect, it sounds like you are describing a problem caused by not knowing the technology/tooling well enough to begin completing the task, rather than a problem directly caused by procrastination.

That being said, one can easily procrastinate the task of learning too :-)

In cases like this, the first item on the to-do list could be a time-limited R&D task where the goal is to learn enough so that you can compose a more concrete plan.

[unfocused828]

> caused by not knowing the technology/tool well enough.

Yes. But given the average quality of documentation and the fact that the most common advice for how to learn a new technology is just to build something with it, how uncommon is this?