1. Don't be scared if the project fails - for whatever reason. Failing can be a good learning experience, if you choose to look at it that way.[see end] 2. Don

1. Don't be scared if the project fails - for whatever reason. Failing can be a good learning experience, if you choose to look at it that way.[see end] 2. Don't be scared to abandon the project. When the work stops being fun ... walk away! You can always revisit it at some point in the future, see if the joy can be rekindled.[also see end] 3. Todo lists are useful ... until they become a burden. I prefer to sketch out some general aims for the project, and some milestones to aim for which I can celebrate achieving. Don't make the project feel like work - unless you really enjoy ticketing up issues and code bugs, in which case: go for it! [see end] - My longest running personal project is my constructed world. I've been working on it for over four decades now: maps, societies, biology, languages ... whatever takes my interest at the time. Many parts of it have been attempted, then abandoned as my mind moved on to the next Shiny. Languages have been started over from scratch multiple times as I realise the current iteration just doesn't work as a "language". I tend not to throw away stuff as I can never tell if it might spark a new idea, a new direction, months or years later. Nobody's ever going to use my constructed world. It will never make any money for me. I do it because the work gives me pleasure - and helps me stop conversations at social gatherings. http://www.rikweb.co.uk/kalieda/index.php http://www.rikweb.co.uk/kalieda/index.php