Maybe you know challenges like '100 Days of Code' or '66 Day Of Data'. These challenges try to establish habits to do things regularly and consistent to make progress in topics you like or need to know.
I started some days ago '100 Days of SAP Analytics' - #100DaysOfSAPAnalytics as a kind of challenge over the summer (20 weeks) to read at least one SAP Community blog a day about a (let's summarise it as) SAP Analytics.
As I'm more in strategy than in implementation of SAP Analytics my focus is possibly very broad. From BW, BusinessObjects BI, SAP Analytics Cloud, SAP Data Warehouse Cloud going to HANA, Data Intelligence, Machine Learning, Conversational AI to topics like SAP IQ or SAP S/4HANA Group Reporting.
My experience is I find sometimes time and sometimes not to read blogs. Sometimes you see 5 interesting blogs published on one day but your day is already full to find time read all of them. Then possibly some of them lands in my bookmarks and stay there for a long time. This is especially true for longer blogs.
In general, blogs help me a lot not just to understand what technologies are for but rather what can be done and when does it make sense to use or discuss them. For me blogs are very useful. But it doesn't help to know there is a blog. I need it in my head to connect it with my knowledge, my experience and other new information about these topic. Therefore I decide to read at least one blog a day (at least Monday to Friday) and send it out via social media (Twitter) to share this.
This challenge even forces me to work with SAP Community blogs more intense than just reading one a day. I maintain a list with all the blogs and try to find the best (from my perspective) about this topic to make it more worth to read it. So I'm a lot in discussion with my self and read sometimes several blogs about the topic and try not to send out something what is already covered or give better insights by other blogs.