> I have more fun doing the hobby itself than I would writing about it.
This is a real problem.
I tend to always have at least one hobby project going on that I know would be of interest to a wide group of people (such as the smartphone I'm currently building).
However, I don't like to document the projects as I go along, because it makes the project more difficult and time-consuming to accomplish, and I start to feel pressure to make sure that I'm providing regular updates -- which turns the hobby into a sort of job.
Instead, I prefer to document dump all my notes and sketches, and put the code and schematics up, after I've completed the project entirely. This means that I don't have a great deal of "work in progress" photos and the like, and that my post is not useful for people who want to see the process of development itself, but it's a compromise that works for me.
This is a real problem.
I tend to always have at least one hobby project going on that I know would be of interest to a wide group of people (such as the smartphone I'm currently building).
However, I don't like to document the projects as I go along, because it makes the project more difficult and time-consuming to accomplish, and I start to feel pressure to make sure that I'm providing regular updates -- which turns the hobby into a sort of job.
Instead, I prefer to document dump all my notes and sketches, and put the code and schematics up, after I've completed the project entirely. This means that I don't have a great deal of "work in progress" photos and the like, and that my post is not useful for people who want to see the process of development itself, but it's a compromise that works for me.