...sometimes I hear people talk about not writing any code to get something accomplished, particular in respect to binding a control to a datasource. They say something like, "...and it took no code to write". For the longest time I was very leery of this particular statement because, often, code is still required. The idea of simply dragging and dropping something and simply expecting it to work seemed bad to me. But, I'm starting to see things a bit differently (but not as I thought I would have had to in order to completely agree with these people).
...first, let's re- (or more clearly) phrase "...and it took no code to write" to "....and it took me, personally, no code to write", and even more precisely "...and it took me,personally, less code to write". There will always be code whenever there is a need to specialize something; and regardless - somebody, SOMEWHERE had to write code (which, again, means bugs). The benefit, however, is that it was written and tested many, many times over - your code, however, rarely is.
The reason why you can never say NO code is because, even when you're jumping through a wizard, you still are required to insert SQL statements, or piece together various statement fragments that eventually combine to offer the solution. This, in a sense, is still code - just declarative and not VB.Net or C# or whatever. It lacks algorithmic fortitude, I guess - but there is still CODE.
Anyway, I'm sure you've read through it before, but check out this article by Dino. Try doing some of this stuff and see how it doesen't prevent code, but simply forces you to think more about the code that you do, eventually, write.
