I think creating barrier to entry is the wrong way to go. Sure, it makes it easy to write bad software (see my signature), but nothing we do will ever stop that.
How often does bad software written by amateur programmers (including database designs and crappy stored procs):
Result in someone being maimed or killed?
Cause the destruction of millions of dollars worth of property?
Cause children to grow up without living parents?
Result in true human terror?
I have to say, it's not very often. But all of the above can be caused by a simple knife. Does that mean we should make knives more difficult to use? Does that mean we should make it impossible to open the packaging on a knife without an expert available?
Personally, I see it as a cost/benefit situation. Sure, some really crappy databases get built. But a lot of small businesses, with "my neighbor's kid is good at computers" type databases, get a lot of value out of those. Some are more expensive than they're worth, but many, probably most, are worth more than they cost. That's really the only measure of any business investment, so I see the low barrier to entry, the ease-of-use, the simplicity of installation, as positive things.
But I have to admit to a bit of prejudice in this regard. My background is sales, marketing, and management/executive function. I got into databases because I needed one. Had it been prohibitively difficult to get one started, or to build something that would "do the job", even if it didn't do it as well as it should have, I wouldn't have worked with databases at all. And I don't think I'm that bad a DBA, as it ends up.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon