|
On Mon, 2 May 2005 16:53:20 -0700 Alan Campin <Alan.Campin@xxxxxxx> wrote: > > > So my questions, why the hell can't we write an > applications that clean on the AS/400? We do we have to > continue writing 10,000 line monolith programs to deal > with abnormal databases? > Alan, First, let me say that the platform used has nothing to do with the normalization of databases. What you saw was a great example of someone with the knowledge and authority (or persuasion to authority) to do it "right" from the start. It just happened to be a non-iSeries group. Second, I hate to say but I agree with what you have seen on the platform is similar to most I have seen. People create applications at the same time or BEFORE they even get the DB designed. Which, is bass ackwards. The bandaid process starts, snowballs, etc. But, what's worse than working with someone with no DB design experience, is someone who is simply "book smart" on the subject, but never appied it. The prior will at least listen and try to understand, but the latter will not. In every shop I've worked with, I would say you're lucky to have 2 out of 10 that understand how to at least halfway normalize a database. I believe a lot of it has to do with the fact that programmers aren't tought DB design. The "fast track" teaching coding, syntax and not much more. Or are "super users" thrown into an IT position because they know how to use Query/400. That's where you will find, again, that the smaller percentage are programmers vs. coders. I find it an absolute JOY to work with programmers, but working with coders, well, isn't much fun. The best part is, you befriend the programmers and end up playing texas holdem with them frequently and arguing programming topics, not coding topics. :) Not to mention, coders are too easy to bluff on the river. ;) Brad
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.