4 ms·
My answer takes from the Feynman approach to problem solving: have several projects laying around that you could easily pick back up to work on a little bit. Th
by wcarss 7y ago
My answer takes from the Feynman approach to problem solving: have several projects laying around that you could easily pick back up to work on a little bit. The progress may not be constant, but it builds over time.
This is a variation on the parent post's suggestion of picking a project you can finish in three days. I find that task can itself be hard, and is work that gets in the way of the fun work. In the past I've burnt out my excitement while trying to do it.
So I have 5+ small games, a game engine, an interpreter and a compiler, a few short stories, some music projects, a personal website, some art projects, and several books to read, and most aren't done.
When inspiration strikes, e.g. I'm feeling musical, I open up my music folder and click around a bit. Or if I feel like making a game, the first thing I do is go play one of my existing half-built games, and pop open the editor. It is helpful here to leave things in a working-ish state and keep ideas around in text files about what you could do next. Make picking the project back up easy for yourself.
I do also start new things or decide not to come back to old ones, but I wound up here by realizing that my interests aren't actually infinite. There's only about a dozen distinct things I really want to do and periodically get excited about.
For years I had been starting and then totally dropping projects, but I had "started making a game" a hundred times. My plan became to treat random projects like turning a ratchet, and I feel it's gone great from there.
- hentaiD00m 7y agoI'm picking up this approach
- imtringued 7y agoHonestly the goal is to just write everything down. When I had been working on some too big to swallow projects during highschool I had lots of ideas but I couldn't implement them quickly. What happened is that by the time I was done with one major feature I had already forgot all the cool features that I planned in my head. Now I just write everything down even if my issues in the ticket system consist of just a title with no body. That way you can stop working on a project for 2 months and pick up right where you left it. The projects end up having a 50:50 split between issues and actual commits. In theory it also makes it easy for other people to contribute.
- RobKohr 7y agoI do a similar thing where I keep a list of things I'd like to do in a list in a markdown file. I put subtasks on them, check those off, and eventually, when the product is done, it gets checked as done. This gives a great sense of accomplishment. Choosing what to do is a challenge for me, so I created a task chooser for when you have trouble deciding what to do next: https://github.com/RobKohr/weighted-task-chooser https://github.com/RobKohr/weighted-task-chooser And you can assign weights to the different things. I usually run it a couple times until it tells me something I feel like doing.