3 ms·
I usually don't upvote pg's comments, because he could say "I like turtles." and get 1,000 upvotes, but pg's advice here is gold. You should do this. You don't
by runjake 16y ago
I usually don't upvote pg's comments, because he could say "I like turtles." and get 1,000 upvotes, but pg's advice here is gold.
You should do this. You don't even need a publisher, you could approach your topic like Zed Shaw did with "Learn Python The Hard Way".
Or you could do a series of blog posts. You WILL get feedback and this will improve your skills.
- davidw 16y agoIf you're only focusing on the 'writing really good code' aspect, sure. But in the wider world, writing a book can be a spectacularly bad way to invest your time. I've made way more money from my "Slicehost vs Linode" article than I have from my portion of "Tcl and the Tk Toolkit, 2nd edition", even though the latter required a ton of hard work.
- aaronblohowiak 16y agoI think the value is in the writing itself, not the monetary feedback.
- davidw 16y agoYes, I acknowledged that - but I think that most people would do well to at least consider the other aspects of writing a book as well.
- projectileboy 16y agoTotally agree. I have a whole series of "Using ..." tutorials that I've written, just for the purpose of learning - having to write in a style where you're explaining something to others forces you to truly understand the subject matter. As an added bonus, you then have some handy reference materials.
- Confusion 16y agoOr you could use code reviews. At work, every few weeks, I'm obliged to start a code review and have others take a stab at my code. Of course I want that code to be nice, concise, readable, understandable, well documented, well tested, etc, because they will all be looking at it very closely. It has worked wonders for the overall quality of my code.