Slashdot Mirror

← Back to Stories (view on slashdot.org)

Evolutionary Database Design

Posted by Hemos on from the jurassic-database-park dept.

Andre Mermegas writes "Check out this article by everybody's favorite object mentor Martin Fowler on database design. Be sure to take a peek at his wonderful books as well."

2 of 171 comments (clear)

  1. The real problem by Anonymous Coward · · Score: -1, Troll

    The real problem is the fact that most DBAs are brainless scumbags. Programmers can do their job - but the converse is not true. Because DBAs are so insecure in their jobs they typically lock down even development databases, resist change only for the sake of resisting and to assert their marginal power, and blame the developers for all their storage problems (like putting data into their precious databases).
    Here's a fucking clue for you DBAs: don't manage the database in the fucking database itself - use a source control system to store the schema and stored procs. That way at least we have an audit trail to highlight DBA fuckups.
    And another thing - any grade 2 retard can use SQL Navigator. I seriously suggest all DBAs start looking for another profession. You had a good scam going while it lasted, but we're all hip to your bullshit now.

  2. Aglie Database = Empty Buzzword by Anonymous Coward · · Score: -1, Troll

    I lost most of my respect for this agile data crap after reading scott w. amblers essays.

    He wrote a whole fucken book on how great it is to put another colored box on the whiteboard before the box marked "database".

    Such grabage... these kind of authors try to ride the "agile/xp/pattern" wave into riches and fame. But unfrotunatly they have NO real content in any of there advice. And what advice they do give is dead wrong.

    As a quick example, Scott gives a worst a best case scenario for database use. the word case is multiple applications using the same database, and the best case is a single application.. What bull shit.. you would think it would be great if you can get multiple applications to take advantage of a single database...

    Next he proposes a solution to this "problem". The solution being the box mentioned above.. well believe it or not, but you have just doubled your work, and made the best case your worst case.. you have now written two applications when you should have written one.