• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Process recommendations for a solo developer working from home

 
Jared Sprague
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello!
I'm starting a medium sized project of reimplementing my coldFusion store using only java frameworks. My store is: www.capoeiragear.com
I'm trying to select a development process that will work well for a solo developer working from home during the evenings and weekends. I may not even need a process for this kind of thing, but it would be nice to have a structured approch for analysis, design, development, testing, deployment, etc.. So my question is does anyone have any suggestions of a process that would be a good fit for a solo developer with no interaction between teams, or have any ideas of how to adapt an existing process to fit my needs? What if any process do you use when you work on solo projects from home?
I'd love to hear any ideas.
Thanks!

Jared Sprague
[SCJP]
http://www.capoeiragear.com

[ August 05, 2004: Message edited by: Jared Sprague ]

[ August 05, 2004: Message edited by: Jared Sprague ]
[ August 05, 2004: Message edited by: Jared Sprague ]
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You might want to consider starting by writing automated tests against the existing application -- something that navigates your store over HTTP and verifies that things work as expected -- and then start to migrate functionality piece-by-piece over to Java, or just build the Java version of the application next to the old one and use your test script to guide you through missing features. That way, you make sure that what worked in the ColdFusion version, works in the Java version as well.

Assuming you are your own customer for the project, I suspect you don't really need a "process" as much as you need a smart set of practices. My stab at a list you might benefit from would be:
1) Write automated tests
2) Have a continuous integration system run all your tests all the time, while you're focused on a specific task and run only those few tests while developing
3) Take small steps and refactor often
 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I like those ideas. I'd add frequent backups and/or a real version control system. Test first is the coolest new idea I've run into in a long time. It's darned hard to get used to but really pays off. And in addition to being a nice coding technique, it has the most wonderful influence on design.
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I fully agree with Stan and Lasse.

Damn sure I would use a version control system, most likely subversion; and I would commit often, up to every couple of minutes.

I would also go with test-driven-development. For a small project I wouldn't even care about manually running the tests any longer: http://pag.csail.mit.edu/~saff/continuoustesting.html

I would also be rather draconic about implementing features in order of value - that is, split features into parts of more and less importance and defer the latter part until late in the project (when you know how much time is left).
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic