I'm sorry if it appeared I came in "guns blazing". I have read other articles by David Poole and normally I think he is right on the money. This time I think he missed the mark.

The article has more of the flavor of a blog/opinion piece than a call for professional discussion.

Where I work we embed databases in our products. Often, before the user requirements are even fully understood, database developers and code developers (who know enough about databases to be dangerous) are busy discussing the database requirements and schema so they can "begin" their work. So maybe this idea of "As a database guy I tend to look at the database layer as the foundations for software development" rubs me the wrong way.

If your job is to maintain the a big OLTP database of financial data that software developers write against you probably won't have easier alternatives to offer them for the near future, so you will have to figure out how to be agile within those constraints. Maybe that is the audience the author had in mind.

I know this is SQL Server Central (database work is part of my job description and daily activity). However, I read the "Central" as a "central place to get information about SQL Server". (Which it does quite well - probably the best! 🙂 )

For many people, SQL Server is one of many useful tools for solving problems and not "Central" to their identity. Information on how to integrate database development into an agile process is useful to those people also. Put yourself in their shoes and ask what they take away from the article "Accidently Agile". Not much I am afraid.