I mentioned in my two previous posts about my foray–no, my unstoppable drive–to a Code Generating approach to application development via Eric Smith’s CodeSmith. I continue to type like the wind from 9-to-5 as I always have, being as productive as I know how to be. But the latenight R&D time on charity coding is where the evolution takes hold.
All I can say after a good week of rethinking and writing an ASP.NET app with CodeSmith is that this code generation stuff sure adds a lot of coding time! I’m being facetious, of course, as I expect great yields from CodeSmith. I’ll start seeing those yields as I move from app to app, using and refining the templates I wrote, becoming comfortable and allowing myself to code and think different. Creating new grooves.
And thus the point of this post: while I have HTML code generated for me at the page level, business objects designed, forms populated, objects packed and data sent to the data layer containing even more autogenerated code, an essential productivity ingredient in using code generators is RETHINKING and REGROOVING one’s coding habits.
I’m a big believer in repetition, so I’ll post back on this subject when there is tangible proof of that rethinking. Another reminder of being a developer is all about the journey.