I used to keep up with 1 post a week for maybe half a year or so. But, for the last year or so I have been struggling with time to keep this up.
I think part of this is due to me not just documenting what I know, but rather going out to learn something and then writing about it. Therefore spending a long number of hours reading other guides, docs and debugging an app and then finally spending even more time writing.
That is something I suggest if you want to write something. Find something you want to learn. Learn it. Then write it up. If you're uncomfortable doing this, then try something small and work up from there.
You might struggle doing 1 a week if you follow my lead, but you will learn a lot yourself as well as writing posts that collate scattered information into a single place.
Hopefully this helps you out a bit 😄
yep. this is actually what I am planning to do. I have a pet project that i am building and i am trying to write some posts summarizing the stuff I learnt and explaining how I built it. but I noticed that that requires a huge amount of time.
working on a pet project is a good way to learn, but often is also consists in reading some tutorials - putting together some snippets and have something working in the end. Writing a post out of it means that you really must have cleaner code and structure and properly must have dug in the stuff you did. ( on the other end, this forces me to really learn out of the pet project - so probably who cares if i skip a week or two... :-)
Exactly. You have to dig into it to make sure someone doesn't tell you your wrong!!
Then the extra benefit is when you forget all this stuff, it's all there on your blog. Written in a way that you understand and with the information that you care about.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.