team C

[FOOTOO]

I am not a professional programmer, so forgive me if this sounds too elementary for you. When I first started the project I am working on, I asked my co-workers for help with the project since it will benefit them, but nobody else would help out, probably since nobody else knew how to program for windows. Anyway, now that I am about a six months into it, I am wondering how I would have divided up the work had someone agreed to help. I find myself frequently updating routines I wrote earlier as I get a better grip on how things should be. So my question is, how do the pros orchestrate the work? They must have some way of dividing up the work.

Just curious

[Dave_Sinkula]

Anyway, now that I am about a six months into it, I am wondering how I would have divided up the work had someone agreed to help. I find myself frequently updating routines I wrote earlier as I get a better grip on how things should be. So my question is, how do the pros orchestrate the work? They must have some way of dividing up the work.

Modular code and version control play a large part.

[Salem]

> I find myself frequently updating routines I wrote earlier as I get a better grip on how things should be.
http://cboard.cprogramming.com/showp...02&postcount=6

[FOOTOO]

Well, if you've never gone back and changed your routines..... You know, added a parameter, added members, revised a process, then either your project isn't very complex or your simply perfect. I know I am not perfect.

[Salem]

You've simply missed the point then.

Sure a good design will mean that you can write the code from end to end without ever changing anything. But even an average design will significantly cut down on the amount of code thrashing that you seem to be complaining about.

Interfaces in particular get a lot of attention to make sure they're right, because they're the ones hardest to change once the code is written. Particularly if you're dividing up the work between several people, a good set of interfaces allows everyone to work to a known reference which isn't likely to change on a whim.

[FOOTOO]

Interfaces in particular get a lot of attention to make sure they're right, because they're the ones hardest to change once the code is written. Particularly if you're dividing up the work between several people, a good set of interfaces allows everyone to work to a known reference which isn't likely to change on a whim.

Yes, Yes!! This is very true. I found a great deal of my time and code to be devoted to fine tuning the gui. It looks good when I sketch it out on paper, but when I implement it, things don't always work well and require adjustment. Also, many of the bugs I had in my computational engine didn't become known until I had enough of an interface to play with things, again causing me to go back and redo things. This is probably not the point you are trying to make, but it is good to know I don't stand alone in this.

Thanks

[laserlight]

I had the impression that Salem was talking about programming interfaces, not graphical user interfaces (or perhaps both).

[FOOTOO]

I had the impression that Salem was talking about programming interfaces, not graphical user interfaces (or perhaps both).

Oh, I think you're right. Just got a little too excited I guess.