Hmm... You kind flip software analysis upside down. But if it works for you, it works for you.
Printable View
Hmm... You kind flip software analysis upside down. But if it works for you, it works for you.
If the amount of otherwise great software with totally atrocious API documentation is any indication, you are probably right. Sometimes I think programmers try to outdo each other WRT just how elliptical, non-sensical, and genuinely unhelpful they can be in the documentation.
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.
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...
LOL... then in all due respect... you really do need to work on that...
One tack, taken from my high school English teacher, is to "figure out how to best represent a given concept in the fewest words"... His "simpler is always better" approach has helped me a lot over the years.
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.