Keep a notebook next to you and write down the thing you want to look at later. Keep doing what you were doing, but now you haven't "lost" that idea, you've just filed it away. Then once you're done with what you originally wanted to learn/do, consult the list for the next thing.

Also works with browser bookmarks, dev.to reading list, github stars, medium bookmarks, etc. Just have some method of filing ideas so they are postponed rather than distracting you now.

 

1) Do yoga and physical exercise, it will help you reformat your brain.
2) Have a motivation for learning that new technology, ideally some project or product you want to create. That way you'll know which information to prioritize.
3) Start with small, working examples that use the technology you're trying to learn in an interesting way. Then, start putting those pieces together in larger contexts.
4) Have both purpose and fun and the rest will fall into place.

 

I make deals with myself. "No doing anything else until this thing I'm doing is finished". When I have that explicit internal dialog, it helps a lot.

 

My problem is to not get distracted while reading a book as example so usually I sue the approach at the night or travelling so there are less temptation from internet.

 

Take it one blog post at a time, 1 book at a time or 1 course at a time. However you have chosen to learn

Classic DEV Post from May 4 '18

Are interruptions really worse for programmers than for other knowledge workers?

This is quite a popular cartoon. I posted this in a comment on why programmer...

Venkatesh bellale
Still working on it..
Join dev.to ❤️

The heartbeat of the software industry.