3 ms·
Huge hobby projects are notorious for sucking the life out of the hobbyist. It usually starts with a strong emotional connection in the form of conviction, visi
by themodelplumber 4y ago
Huge hobby projects are notorious for sucking the life out of the hobbyist. It usually starts with a strong emotional connection in the form of conviction, vision, and probably way too much patience with oneself.
Then the patience goes, the vision needs adjustment, and finally the conviction is in doubt...
So good job hanging in there.
Here are things that help me:
- I encourage myself to b*tch about it, especially if I am passionate about it. Never did this before but it's just a fun alternative to being too serious...and still being annoyed. And if you have even the tiniest amount of bad == good reverse psychology, this will be giving yourself energy by definition. "I hate this piece of sh*t hobby! God what a waste of--" (suki no uchi dazo)
- I use micro-passions instead of micro-visions. I put it aside until the next wave comes. If I'm afraid the next wave won't come, I rank the micro-passions. Like break it down to 5-10 components (at least) that you like, and then rank them by how much you like doing them. (Not how much you like completing them) From there it becomes a question of surfing the waves as they come.
- Human psychology is really, really primitive in terms of its use of interest-symbols as pointers to deeper insights, so you can sometimes take advantage of it. Study what the specific hobby-topic says about your life, and what it's suggesting. This can help you be less serious about a hobby, even if you're still interested in it (== better able to commit steady, patient interest to it over time). IOW you might realize "I'm building and painting model cars because my mind is hitting me with a clue-bat, suggesting I can maybe design an enjoyable life where I'm in control of the wheel and actively going somewhere" is a surprisingly a) good fit to one's subjective reality sometimes and b) disturbingly funny insight into where you're at. You can start with a dream dictionary since those are really just symbol dictionaries.
- Document your progress, this is huge. If you lose clarity on your next step (of say, 2-5 minutes length) it's easy to get derailed. If you lose track of your personal method because you never documented it, ditto. Nobody wants to re-figure-out that stuff. I make sure there's a how-to component and a logging component as well.
One other big one:
- Keep a list of your interests. What happens is, you'll discover that you're always in the mood for _something_ so if you like lots of things, you'll effectively never be able to lose touch with your passions. And this feels damn good. "Ah damn, my hobby nuclear reactor isn't feeling interesting today, good thing I have been needing to put in some time on my donut-critic hobby!"
Hang in there, and may your visions come true in ways that force a good cackle.
- __d 4y agoI like the "put it aside until the next wave comes" approach. I have many hobby projects, ideas, partly-built things. I have some that are very near to completion, and others that are probably a lifetime's work. I tend to work on them in short stints: a few nights, sometimes like a month or two. And then set them aside as I burn out on that idea, or come up with a compelling extension/revision/use-case/etc for a different one. It's really crucial to document where you're at in this model: you need to be able to pick things up again without too much time to figure out where you were. I have two things that help with that: Firstly, a README.md file for each project which includes my roadmap, with stuff crossed off as I get it done. So I can pull it up and see exactly what's next and what I just did at a glance. And secondly, I keep a (large) journal.md file, divided by date, where I write down what I did. Especially stuff that I needed to research to figure out. That includes literally copying command lines out of my shell and into the journal. It's just a massive bulleted list, but when I restart something, I can quickly search back to the date of the my last commit, and see exactly what (and how) I did the things I did in that burst. Combining my roadmap/README, journal notes, and Git history generally means I'm productive again in about 15 minutes.
- mronetwo 4y agoThis is how I go about my projects. I can't say I'm at peace with this approach though. I feel like context switching makes it that I won't finish anything during my life time. Anyways, documenting projects for yourself is very important. Treat your future self as best as you can. Think about the problems your future self my encounter.