3 ms·
> monetizing hobbies I find two issues with this (disclaimer, My "hobby" is coding, so I guess I've been monetizing it, all my adult life): 1) Once someone st
by ChrisMarshallNY 4y ago
> monetizing hobbies
I find two issues with this (disclaimer, My "hobby" is coding, so I guess I've been monetizing it, all my adult life):
1) Once someone starts paying you, they get to exert their influence on your work, and it becomes a lot less "hobbyish."
One of the biggest joys in my life, these days, is not having managers destroying my work.
2) Delivering ship software requires a lot of "not fun" stuff.
In some cases, the majority of the project could be wrapped up in "unfun," like needing to use particular coding practices, languages, dependencies, techniques, etc. Also, there's all the "polishing the fenders" kind of thing, like documentation, UX finish, maintenance, fixing all those bugs that you don't think are "actually bugs," establishing CI/D, configuration management, presentations to the Board, etc.
These days, I write software for myself. I eat my own dog food. Every one of my projects is a complete ship product, with all the aforementioned stuff (without the CI/D, as I don't really need it, for my one-man shop).
- scambier 4y ago> 1) Once someone starts paying you, they get to exert their influence on your work, and it becomes a lot less "hobbyish." Definitely. I've been working on a free open-source project for 6 months. Last week, a user came with a feature request, and stated that they were willing to pay me. That could sound nice, but I immediately thought "nope". I told them that donations were appreciated, but I wasn't going to do commissioned work. I don't want that kind of responsibility for my hobby projects.