David Freeman david_freeman@rocketmail.com writes:
No somebody who has learnt the hardway that you need to design the code, if nothing else to design the bugs out. I'm not ont for creating BIG designs etc... just nice highlevel concept diagrams and other USEFUL things like that.
Yeah, pretty pictures. Everyone likes pretty pictures. 'cept me. I'll take a good explanation over a specialised diagram requiring a key almost any time.
How can you say that? I originally posted a relational scheme to the list and was told tht it was naive and was lacking and some other scheme were posted, had we designed it correctly we would have the scheme ok first time round.
http://rabbit.stu.uea.ac.uk/pipermail/alug/2001-May/001083.html
Only Brett seemed to criticise it...
[...] What we must avoid like the plague is making assumptions, any engineer ot scientist will tell you that an assumption is the mother of all f*** ups.
What am I? A pomegranate?
Good code is code which meets the needs of the application and doesn't crash. [...]
Being written is a prerequisite for these.
Good. For now we need to just assume we have a RDBMS until the point when we have the design done.
Is an RDBMS appropriate, or should we just assume an OO backing store?