Same as usual:- Have/get/find/ask an idea- Start early- Document while coding- Add features sparingly but complete- Test, test, test (and fix bugs/refine features)- Test some more- Release just in time - Update after a few days/weeks to make feature complete and bug-free

Well, what I found this year was that working on something way in advance (and not specifically for NANY) helped. Usually it's a scramble at the last minute, and it still was as I was trying to get my other pledge done. But I like to pledge rather than just show up so that it gives sort of a head count.

Testing is one of those things that I do as I go along, and then again at the end. You can never really test everything, unless you have a LOT of time and money to do it. Hardware, drivers, etc. etc. etc. It never ends. I had an MP3 playback error years ago... it was a driver issue that I couldn't do anything about - thank god it's gone now.

My typical NANY method, and mouser can confirm this, is that I don't do pledges; I just do releases. I had less time this year than in years past so I was only able to release one app (and a simple one at that).

I made PCA since I used to get irritated by the stubborn cursor. OW was made to have my dear one's photo on any wallpaper. SAN and TWD solves my problem of forgetfulness.

The MCAT in this year NANY helps to speedup new project development.

All these apps solves my problem and I hope, may help other users too. NANY and DC gives me the platform to showcase them. One thing I learnt this year is 'do not wait for the NANY to begin, but start your engine as soon as you get time'.

Well I am facing one more problem and could not get time to solve it. Hope to release as non-NANY in coming months.

Well, what I found this year was that working on something way in advance (and not specifically for NANY) helped. Usually it's a scramble at the last minute, and it still was as I was trying to get my other pledge done. But I like to pledge rather than just show up so that it gives sort of a head count.

Mouser is pondering to take the Last Minute Scramble part out of it, and let it be more of a year long process. As seductive as the calendar New Year is, it also just happens to be the busiest holiday month which can't help scheduling dev time on the app.