The web is supposed to be this great leveller. Everyone is able to publish whatever they want and put it before a global audience. There is no bar to entry into the web club. Sometimes that might not be seen as a feature.
We all know HTML "designers" who have no idea of how HTML should work.
As Perl programmers, we've all seen CGI programs written by "programmers" who have no idea how to program.
I'm now starting to see more and more web sites that include databases which have been "designed" by someone with absolutely no clue about entities and relationships.
Take, for example, the database that I'm currently replacing. It's a music database so it models (amongst other things) artists and tracks. An artist has a number of associated tracks.
In my design, there is a table called "artist" and a table called "track". The artist table has a primary key and the track table has a column called "artist" which contains the key of the artist associated with that track.
In the original database there was a table called artist. The track data was an attribute of the artist. And when I say "attribute" I mean that there was a column in the artist table called "track" which contained a comma separated list of the tracks associated with that artist.
But it gets worse. A track has attributes - the track name, the name of the MP3 file it is stored in and a boolean flag to indicate whether it has been approved by the A&R people. So the artist table needs three columns for the track-based data. The "track" column I mentioned before contains the filename. There are also columns called "track_name" and "track_approved". Each of them are comma separated lists of values.
And in some cases, the number of items in the three lists isn't the same.
This is a web-based system that was designed and implemented by another company for my current clients. People are being paid to design systems as badly as this.
Am I being too critical? I've been working with databases for far longer than I've been working with the web or Perl. Database normalisation is second nature to me. Is it too much to ask that people who are designing databases actually know something about... er... designing databases?
 Which was in Microsoft Access, but I'm not drawing any conclusions about the abilities of Microsoft users in general.