I'm not sure if this will make sense, but I've realized how much extra time it takes just to include a new column in my database.
Of course, this column is used in many places in my code, so that's why it is a burden to simply add only one.
Say I have a complicated, but not over-complicated web app in asp.net. There are about 30 columns in my database which I want to be able to edit through asp.net. The best way I know to query the database is with a stored procedure, which I am saving in the database, not implementing in application (not important, still takes a lot to modify in either case). Then I have a (basic) form in my application that has something like textboxes for the user to see the current values in the database and is able to change/save new values. I do understand something like a gridview can cut back on coding, but that still doesn't change my point.
Say I want to either remove a column( ...
Go to the complete details ...