Thread: How do I plan and run a software project

Originally Posted by CommonTater

It's not what you see in the code you just wrote... It's a matter of coming back to it in 6 months or 5 years, after moving on to other things and having to recall what you did.

I know that... I've got a problem to write comments and documentation in a clearifying and meaningful way. When I get back to my comments (or documentation) in a couple of months, I just go "what the f...". They are useless, no matter how much effort I put into them.

Originally Posted by Mario F.

Hmm... You kind flip software analysis upside down. But if it works for you, it works for you.

Analysis is different than writing code...

In the early phases before "int main (void)" I work from large to small... deciding requirements as I go. So by the time I've tunnelled into the problem far enough to understand it properly, I've pretty much already designed the UI and at least the larger blobs.

Then in the writing phases it's a matter of "I need this working before I can get that working" so the order of things changes quite a bit. As I said, in windows you aren't going to do much of anything without a working UI...

Thank you MK27 for your tip... You've got me right there, with the re-using variables and rather using scripts than make files. I'm buying your concept straight off.

You're more than welcome to share more thoughts.