After few months after going through the book, I started noticing that it takes me more and more time to read, exercise, summarize and publish new articles.
Hence, felt like sharing with you some difficulties I did encounter over the past period and why I am thinking about experimenting with another approach.
it's time to take a step back and start looking for a better, simpler, and faster approach to share the different learnings in a consistent way.
Despite the goodwill, It can actually:
- take up to 2 weeks to find slots, outside my working activity, to fully read and understand a chapter.
- then, another 1 to 2 weeks to work on the exercises, sometimes just walking through the solutions.
- finally, taking at least another 1 to 2 weeks to summarize the chapter and then publish it on the blog.
In summary, almost 2 months for a publication, worst case 3 ! 😂
This is undoubtedly everything but optimal, pulling too much effort and attention on one topic, and I wouldn't recommend it for anyone. It's a time killer and a frustration amplifier!
In parallel, it is usually recommended to keep a blog active with frequent updates and with an average of a drop per month.
I could observe that Intermediate bloggers do usually publish content once every two weeks, while seasoned ones do publish updates on a weekly basis and can go up to one per day. The other observation is that seasoned bloggers, keep the article's content short with a consistent format. Avoiding TLDR!
Outside the nice idea of becoming a professional blogger one day 🙂 , I am looking for the right balance to:
- Share frequent updates over shorter periods: weeks over months.
- Find slots to go through other books I would like to enjoy reading, experimenting with described techniques, and ideally sharing with the community.
- Do other stuff/hobbies aside blogging and working: playing guitar, hanging out with friends, a normal life 😅
So long story short, it's time for a change and a better organization.
Going forward, the chapter summary will have the following common structure:
- Chapter title: as in the book
- Purpose: introducing the governing idea
- key sentences: as in the book
- key takeaways: list of attention points
Things that won't be included anymore:
- Code examples
- References to frameworks: scikit-learn, tensorflow, etc..
I hope that you will still find the next articles useful despite shrinking.
Please feel free to comment may you have suggestions for a better approach or structure.