What are some solo developer programming methodologies? [closed]

Answer 1

Just about any development methodology will work in a solo environment except for those that explicitly require a team (such as side-by-side programming). But even then you could get around that by just creating some imaginary friends/teammates or developing a multiple personality disorder.

Answer 2

Even as a solo developer you can use methodologies applied to large development teams.

• Write a Spec.
• Layout a UML.
• Do pencil-and-paper UI design.
• Hallway testing: If your expect a large crowd, ask Mom if it's easy to use.
• Peer review: You can build ad-hoc review teams with other solo developers.
• Keep an up to date schedule.
• and so on...

I solo develop all the time, and these practices keep me in line with my own work and give my bosses a great resource to know what I've done and how far along I am. And they keep me on track, to boot!

Answer 3

The rubber duck methodology comes to mind: http://lists.ethernal.org/oldarchives/cantlug-0211/msg00174.html

Answer 4

Follow what is laid out in this Stack Overflow question:

What Tools/Techniques can benefit a solo developer?

Also. Use Source Control. You wouldn't believe how many times I've been bitten by that on personal projects.

Answer 5

The issue is more a question of what you are comfortable with and what problems you hope to solve. Most methodologies are used by a solo developer at some point (pair programming is a notable exception). The issue is are you actually alone, or just working by yourself? I have found that it is invaluable to have people I can bounce ideas off of. Furthermore having someone else to look at you code (peer review) is a great way to find issues that you just cannot "see". So to agree with Aiden Bell "Programming on your oen is uncool." I would try and connect to a community (like SO) where you can bounce ideas off of others. Then you need to build your methodology in such a way as to allow for interruptions when you send an idea out.

Does that make sense? Why are you programming alone?

Pat O

Answer 6

There's this:

http://en.wikipedia.org/wiki/Personal_Software_Process

It's probably overkill