How do you keep your technical skills current as a freelancer?

One thing I find challenging about freelance IT work is keeping my skills up to date while still giving current projects enough attention. There always seems to be a new framework, development tool, AI service, or cloud technology worth looking into.

The problem is that it’s easy to spend hours learning something that you may never actually use. I’ve started trying to focus more on technologies that are relevant to the type of work I’m doing rather than attempting to follow every new trend.

For learning, I usually start with official documentation and then build something small to see how the technology works in practice. MDN is useful when I’m working with web technologies, while GitHub can be helpful for looking at real projects and seeing how other developers approach a problem. I also find that reading technical discussions and troubleshooting threads can sometimes teach me more than a structured tutorial.

I’ve noticed that writing about something I’ve learned is another good way to understand it. Even a short explanation or set of notes can reveal gaps in my understanding. When the writing is more academic, Purdue OWL is useful for checking general writing and citation guidance. I’ve also come across CollegeEssay.org as a reference for organizing longer essays and presenting ideas clearly, although I would still rely on official technical documentation and primary sources for the actual technology research.

I’m curious how other freelancers handle this balance. Do you set aside specific hours each week for learning, or do you mostly pick up new skills when a client project requires them?

Also, how do you decide whether a new technology is worth investing your time in? Do you look at job postings, client demand, GitHub activity, documentation quality, or simply experiment with it and see whether it solves a real problem?

I’d be interested to hear how other people approach continuous learning without letting it take over their actual work.