>You're right, customers don't care about what tool was used to build something, but they care that you can do your job well and good tools help you do that. T

>You're right, customers don't care about what tool was used to build something, but they care that you can do your job well and good tools help you do that. True, but I do my homework too. My code needs to be maintainable for the next guy. We can't invest inordinate amounts of time on V2 where it isn't necessary. I don't want unrelated parts of the program breaking because I fix a bug. The next set of features should be easy to implement from an architectural perspective. All of this is important to the customer and my business. I care about my craft, but there's a line at which I stop investing my time in debating the toolset. If I'm spending ~10 hours / week writing blog and forum posts about why everyone should use X framework instead of Y I'm seriously wasting my time.