I agree with the angle of this article. However, I am a developer. I mainly write entire applications and websites by myself. I used to lead a team. Regardless of which setting I am/was in, I always make sure that the database design gets the utmost consideration. I took the time long ago to learn everything that I could about good DB design.

I am a stickler for consistency and standards, so I have always had guidelines written up for my team (even when my team is just myself) on how to handle just about everything from naming variables, functions, classes, columns, tables, indexes, to how to arrange an argument list, use of tabs vs. spaces, and where to put block begin/end indicators (on the declaration line vs. below it, etc.).

Attention to proper design and careful implementation are key to the long-term success of a project. I always find myself correcting colleagues' inconsistent column names, or mixing tabs with spaces. The usual response is, "What does that matter? I just want to know if you think it will work!"

It seems as though many people in our field do not value organization, planning, and general forethought. It's a shame. The software suffers and its users learn to accept certain (inexcusable) patterns in its life-cycle.