Try It Now! Video instruction manual for too many tech workers!
If you work with databases, you must look at the data.
Don’t create the wrong object. I’ve seen some strange “designs”. Ie. Another database was created instead of a schema. A table was created instead of a simple function. A series of five tables and views was created when a single field would have sufficed!
Another Database Design Mistake to Avoid Recursive programming is used in a few places in computer science. Most notably in…
The rule of thumb for the number of tables:
Many to Many (M:N) 3 tables
One to Many (1:M) 2 tables
One to One (1:1) 1 table
The unfortunate thing in database designs is that unlike programs, they are rarely, if ever, reworked. If a program doesn’t compile, the code is corrected until it does compile. And then if the program doesn’t produce the right output, the code is again corrected until it does. I’ve seen one relatively simple program be refined and put into production at least eight times. … The database design is usually thrown up as quickly as possible …
A great creative idea, executed poorly, would be crap. You wouldn’t get paid, and you wouldn’t get any referral business.