Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.
I periodically enjoy working on side projects. Not just messing around, but a full blown side project that has some set of features that I think would be useful. I never have any real intent of releasing them so I don’t ever put too much priority on them. Usually what I take away from them are knowledge of new tools/frameworks/libs/patterns etc. Althoguh they aren’t always completely new to me, they may just be deepening my current understanding. For me these side projects go into three states:- I get really into it and work on it non stop for a few weeks.
- Once I finally get over the fun parts and feel like I stopped learning, it ends up sitting quietly in a half working state.
- I abandon the project completely because I’ve thought of something else.
- Go to step 1
Almost always option №1. Can’t resist to try some new library or framework, when working on some idea. 🙂
I generally do as well. It’s just been more recently where I’ve been thinking about it. Especially since what I’m after is getting something out there to validate the idea. I feel like using the tools you know in that case gets it out of the way so I can move on to the next thing. Easy for me to say, because never do that and always try something new!