How Do You Develop Software?

[Squidge]

Ie; What do you do when you start a new project before you start writing the source code?

Myself, I normally note down what I want to do, and how am I going to do it, explaining each process in as much detail as possible, using diagrams to show how the program would normally execute. If it's a GUI program, then I normally sketch a few screens of how it should look. Once I'm happy that is satisfies what I want to do, I then start coding, and constantly refer to my notes and diagrams, updating them as and when necessary. Eventually I end up with a bug-ridden piece of software

 

[woogal]

What do you do when you start a new project before you start writing the source code?

Wake up, drink coffee, maybe eat some cold pizza.

 

[skysnapper]

What do you do when you start a new project before you start writing the source code?

Wake up, drink coffee, maybe eat some cold pizza.

​

At work used to be

1. Meeting/Breif
2. Specification including screen layouts
3. Model it in Select tools
4. Test Plan
5. Walkthrough with team

ermm these days we have got very slack...

meeting/email/chat with user/work of a scrap of paper

Just do the whole lot on the fly....

Although had a meeting last week to say we got to go back to the old way of doing it ...YAWN! :rolleyes:

 

[Axeman]

ALGORITHMS

 

[EvilDragon]

I'm one of those crazy guys who have an idea and start coding it.
Then I encounter some problems on the way and code some subroutines as a workaround for these problems.

When finished, I have a messy code with a lot of workarounds - but working.

Then, it usually happens when I'm not at the computer and doing something completely different, I know what I did wrong for this and that problem, start to exchange the routines and get rid of the subroutine workarounds.

Eventually, the code is fine after a few weeks

That's probably why I'm NOT the right person if you want to start a large or Open Source project...

 

[Octavious]

well, for tools, I use other progs
gigas , doombuilder , anything non-coding like
havnt learned to code yet, but still tryin to help the comunity
but for the order

Get an idea
try and find another similar idea
get lots of info
for example, I was doin a perfect dark doom till gpquake got good
I was thinkin bout doin a metal gear solid doom so I thought up another, perfect dark
then thought about which one would be easier to map
metal gear solid
which one would be easier to get weapons from
perfect dark
enemies from
both easy , metal gear easier to make , perfect dark just more types
less map editing ( wasnt good on doom builder yet )
perfect dark
which would look best if converted
perfect dark
more gun types?
perfect dark
many more options, perfect dark

SOOO...
I went perfect dark
then I mapped out enemies guns levels and more on paper
didnt need a story like I do with gigas games
then started with maps to see if doom builder would get the right look

long story shot
idea
counter idea
pick best one
lots of random info gathering
start with levels first on anything I think ( well, in my few scenarios )

But Final war was all diferant , tell yall bout that later ( its differant in teams )

~Octavious

 

[Squidge]

Interesting collection

Does anyone use models to simulate the process flow of an application?

 

[PinkSpider]

When I used to code at college we had to use JSP then some other boring techniques I couldnt remember. Didnt really help cause the programs where fairly basic; then bloody testing and shit.

 

[lizard808uk]

Ive used SSADM, RAD, DSDM, Blueprint, Black Box, White Box and a number of hippy ones too. I then usually give it to the code boys to actually do it.

I've found the best way to design something is to mong out next to the coffee machine.

 

[PinkSpider]

RAD - how I hate thee.

 

[generalnmx]

Sometimes I jot down notes, but usually I just keep the design structure in my head. If I want to write it out, I just make prototypes with notes on what they SHOULD do, instead of using psuedo-code.

I've worked in groups before, and true psuedo code usually ends up confusing people. I just make notes if it's suppose to do something. If I were working professionally, I'd have to abide by whatever guidelines the company sets down. But if I am coding as a hobby, I tend to go by my own style. But I document my code well enough that I don't think it's a problem.

 

[PinkSpider]

I hate pseudo code.... I used to love coding and working out problems and shit but hated the documentation etc.

 

[Squidge]

Without the documentation however, you normally end up writing crap code and fudging it afterwards when you find out what you missed out.

 

[PinkSpider]

Indeed, but I generally find it more fun working that way; I used to lie awake wondering how to get code to work. Granted this was all simple stuff; VB/ Pascal but I used to enjoy it. Our teacher used to kill us if he found out we hadnt done the Pseudo code etc.

 

[Anox]

well, when programming something in java or visual basic, i first think of what it should do and how the whole process could be done. then i start coding. i really think that it helps alot because you dont have to think so much about how it works and you can concentrate more on the actual coding itself...