frontend

What I Learned From a Year of Deliberate Practice

Thoughts from the intersection of code, craft, people, and progress.

Looking back at the habits that made the biggest difference this year.

Deliberate practice sounds rather serious, but in practice it mostly meant choosing a few skills and returning to them consistently. The useful results came from small repeated efforts, not a heroic weekend spent becoming a completely different engineer.

The useful question behind “What I Learned From a Year of Deliberate Practice” is what changes in the work afterwards. A sound idea should improve a real decision, not only give us a neat phrase for describing it.

There is a practical tension underneath this topic: we want enough structure to move confidently, but not so much that the structure becomes the work.

Progress needs room around it

It is tempting to treat progress as a question of effort alone. In practice, energy, confidence, context and timing all shape what we can do. Ignoring those things does not make us rigorous; it makes our conclusions less accurate.

I have become more interested in sustainable habits than heroic bursts. A modest routine that survives a difficult week is more valuable than an ambitious plan that only works when life is unusually cooperative.

Sustainable progress is still progress, and it tends to last longer.

There is no prize for making useful work unnecessarily painful. Keep enough space to notice what is working, change what is not, and enjoy some of it.

I do not always manage it perfectly. The aim is to make the better choice easier to recognise the next time it appears.