All excellent points. It was a little hard for me to give up some of the 'homegrown' framework stuff I'd built (and tried to commercialize) over the years (in the PHP world), and I've not totally embraced any one PHP framework/library out there as a replacement, but using *some* tool that has a much wider audience and is considered a standard has a lot of social and business advantages that I didn't see years ago.
1. easier to work with other people - sort of.
2. easier to transition work away to someone else - yes.
3. easier to respond to job/contract work that require "MVC" (telling them I wrote my own 3 years before any of the current crop of frameworks was even started doesn't compute with most of them)
So... I get your movement towards
ASP.NET MVC. I've seen some interesting stuff crop up there - the view engine 'competition/evolution' (spark, razr, etc) for one. It's amazing how similar most of the ideas between frameworks really are, even if most of the users have no clue.
There's a balance between 'cutting corners' and 'optimizing my effort' which... I have to say, I'm still developing after all these years. I've gone back on projects recently from 2-3 years ago and been embarrassed at. I make fixes in a few minutes, when I know at the time I knew there was a 'better' way, but also knew it would take me hours or days to research/test/integrate correctly, vs the hack I used. Certainly I have that knowledge 2 years later, and it's just a few minutes (and in some cases, the tools are better now), but I tend to feel like I cheated the client somehow, and they're having to pay me to fix my own 'mistakes'. Objectively I don't think that's the case, but there's a bit of protestant guilt I was brought up with - everything's my fault all the time - so... I struggle with that some.