How to Code for Fun Outside of Work

I, too, was doing Project Euler problems for a while, but eventually I realized that with the same amount of work I could be making things I actually want to use. My Project Euler solutions were conceptually on a shelf, sitting unused. It didn&#x27;t feel too good.<p>On the other hand, on Sunday I wrote a simple mode to upload code to an Arduino from inside Emacs (<a href="https:&#x2F;&#x2F;bitbucket.org&#x2F;zck&#x2F;zarduino.el" rel="nofollow">https:&#x2F;&#x2F;bitbucket.org&#x2F;zck&#x2F;zarduino.el</a>). Now that&#x27;s fun.

I really enjoy constructing projects spun off Python Playground from No Starch. Unfortunately that book contains &quot;the answers&quot; as part of the book, but sometimes the author gives interesting directions for further exploration (or I simply use his ideas as a starting point for my own projects).

My problem with personal projects is returning to them after a few weeks have passed. I typically end up re-coding the entire thing from scratch (by scratch I mean starting from a blank editor and copying&#x2F;pasting blocks from the old file until I can grasp the mindset I was in when I first wrote it -- this is a very counter-productive process [although sometimes I come across fundamental flaws in my former thought&#x2F;problem-solving]).