2 ms·
I'm personally playing with the idea of starting a blog, not a book, in the mid future. I have tons of unpolished article drafts laying around. On one side I'm
by dgb23 5y ago
I'm personally playing with the idea of starting a blog, not a book, in the mid future. I have tons of unpolished article drafts laying around.
On one side I'm painfully aware of the work required to write useful texts and the monetary incentive is almost non-existent. But what motivates me is to finally take a leap to try and be competent at writing in English, which is not my first language. As of now I'm terrible at it and I feel having a real project that people might consume in some way might be the best way to really learn that.
Secondly I think being able to communicate ideas clearly in an engaging fashion is very beneficial for someone in our field. Writing better documentation, clearer code, comments and specs all depend on that.
A book is a different undertaking all together in terms of scope and polish, but my guess is that the benefits might be in a similar category.
- m-i-l 5y agoI can recommend starting a blog. The big thing, at least for me, is it that incentivises you to finish side-projects and complete thought pieces (at least finish/complete them enough to be able to write about them). Prior to starting my blog I'd years and years of unfinished and undocumented, but potentially quite interesting and/or innovative, side-projects. Just to add - for technical folks a blog can be free and relatively easy to setup and self host with something like Hugo or Jekyll on GitLab or GitHub pages.