I don't understand the concept of paying for the sins of your fathers, but I DO understand the concept of paying for the sins of the code I fathered.
Today I've been writing an ASP.NET app based heavily on an app which I wrote just 6 months ago. Maybe its because I've had a great 6 months and feel my coding has improved quite a bit since then, but my god, what a mess. I was making my first attempts at techniques I'm doing everyday now: inheritance, code generation, business objects, layered app design, reusable function libraries, so on.
The good news is that I know my work is cleaner and smarter now, so that's something. And perhaps that growth will continue. While I think the code I'm writing now is pretty smartlly written (relatively speaking, anyway), I suppose it would actually be beneficial for me and my employer if I were to look back in 6 months on the code I'm writing today with similar sentiments.
Still, its painful to have to look back at where I've come.
Sometime later that same year...
Still, its painful to have to look back at where I've come.
Or maybe not.