Re: What is YOUR Development Process?

The posters above said a lot of useful stuff about technical details. I'll focus on something else:

First I take paper and pens and start drawing. That's pretty old-school and may sound odd to some of you, but I like to sketch my classes and tables and whatsever on paper - and if I change something I redraw the necessary parts. I need to see what I'm doing (that's also the reason why I like Data::Dumper and GraphViz and ...). If I have to stop my work for quite some time - to work on some other projects, I just have to look on my papers if I restart working on my project.

Comment on Re: What is YOUR Development Process?

Replies are listed 'Best First'.
Re^2: What is YOUR Development Process? by philcrow (Priest) on Nov 07, 2005 at 21:21 UTC
I forgot to mention the drawings. They are sitting right beside me. I have a data model (second draft -- project started last week) and screen shot mock ups. If object interacation or network communication gets complicated, I'll make a sequence diagram or two (with UML::Sequence). Or, I might just make an outline of the proposed callstack/protocol in a text file. Phil	[reply]
Re^2: What is YOUR Development Process? by spiritway (Vicar) on Nov 08, 2005 at 02:44 UTC
It's certainly "old-school", but then again, so am I. I'm not a professional programmer. It's a pasttime for me. However, any time I undertake a non-trivial project, I get out a small journaling book to write in, and first work out the general scheme - diagrams, flow charts, if using a GUI then a general sketch of how it ought to look. Over time I update the journal, but at no time do I really do without it. This may be more a reflection of how I was taught (mostly on paper), than necessarily a good idea.	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks