Personally, I agree that flat file db systems are definitally not scalable. To the extent you seem to be considering. I wonder how
PM would run with flat files. :)
Regardless, I suggest you write. Write a
lot. Spec everything out, and read over it. Create a data model in excel, with table layouts, (or flat file(shudder) column layouts), and program flow charts. Even writing a simple paragraph
in plain english helps me clear my head and move foward a bit. Sometimes you realize what you can do easier, and what you simple cannot do, by writing and specing (if only to be viewed by yourself) things out before coding.
I hope this helps. I spend many-an-hour in meetings here at work, and most of the time I come out knowing what priorities I have to restructure, and usually end up productive that day..
_14k4 -
webmaster@poorheart.com (
www.poorheart.com)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.