Code.Implant

I was blog browsing a while back on the 47 Hats blog and found an interesting blog entry that speaks to a question I often see online from small developers: what’s a good process for me?

The entry, "Process and the microISV", highlights four practices that help with small developer success:

1. Hold weekly business and technical reviews. This helps you from veering too far off course from both a business and technical perspective. As I mentioned the other day, it’s important to stay the course in any development project, but critical to remain focused when you’re a small developer with limited resources.
2. Define clear end-points. This is basic goal setting. Define your vision and identify the steps necessary to achieve it.
3. Create a work schedule (and stick to it). This pertains more to those working at night in addition to the regular day job, but it’s critically important for two reasons:
   1. A work schedule can actually help make you more efficient. If you know you have a limited amount of time, you’re probably less likely to slack off.
   2. A schedule can also help life outside of work, as it allows you to ensure that you have free time for things like friends, family, and personal time. Work-life balance is important.
4. Keep a "Not Now" list. Again, focus on what’s important now and what can wait.

These are good common sense ideas, and since I found the list I’ve been trying them myself with success. If you are struggling with staying focused and getting your projects done, then you may want to give them a try, too. 

Note: A "microISV" is a term coined by Bob Walsh, owner of 47 Hats, and it literally translates as "micro independent software vendor". Basically a microISV is a small software developer of no more than a few people that builds applications not for the multi-million or billion dollars, but enough to live off and be their own boss.

Filed under: Development, Process