11–20 of 21 posts
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 HT…
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 HT…
How do you know that you know "enough" on a topic to write a book on it?
An overdesigned, overengineered personal website
It is fun to develop, rewarding and the dynamics inside the code are always interesting (input from the player, performance, graphics, etc).
Even a simple game that can take an afternoon or a day to develop bring some fresh air.
I would also second the recommendations to write a game. If for no other reason than the fact that it is some of the most fun programming there is, you usually get to flex muscles you'd never get to in a boring web dev job.
* performance analysis/monitoring tools. Most developers are astoundingly bad at performance and then lie about it with weird unfounded guesses
* markdown to html parser or the opposite. Most developers have no idea the actual cost of involvement required for basic string parsing and wrongly believe it’s free
* network proxy. Aside from authentication this is mind blowingly simple. Most developers will supremely over engineer this
* API documentation. In a world where the average developer struggles to write an email actually describing inputs, purpose, and outputs clear enough for a stranger to follow can be quite the impossibility
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 HT…
How do you know that you know "enough" on a topic to write a book on it?
- 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.
-