[mooreds]

I think writing a book about something technical. Either self-published (I like leanpub) or through a publisher. Doesn't have to be long, even a 30 page ebook is a big effort.

I have done this a few times and you learn so much and appreciate so much.

Other than that, I think it really depends on where you are starting. If you are a webdev, building an MVC framework. If you are a system programmer, building a basic HTTP.1/1 web server.

[FireSquid2006]

How do you know that you know "enough" on a topic to write a book on it?

[mooreds]

My process for any book I'm thinking about writing is:

- write out 10 titles for blog posts on the topic

- write 1-2 blog posts (this lets you see if you have interest/expertise)

- do a bit of research to see if someone else has written on the topic (some googling or reddit searching

- write the rest of the blog posts

If you can't write 10 blog posts about a topic, then you don't have either:

- the interest in the topic

- the knowledge in the topic

If no one else has written anything about the topic, it might not be worth writing about, but you also want to make sure your take is unique enough to be worth your effort.

-

[brudgers]

Maybe by researching until it feels like you do? I mean sometimes writing can be a learning process, not just a teaching one.