Do you think it’s worth trading off some performance for code-quality and maintainability? I remember a post by Jeff Atwood that stated that hardware is cheap, developers are not. I think I’d like to change that to ‘Hardware is cheap, time is not.’
I’ve noticed with an MVC project I’ve been working on lately that sometimes I lose DAYS just trying to squeeze out a little extra performance out of my app and I’m starting to think it’s just not worth it. I’ve just found myself having trouble with designing an ASP.NET MVC application. I love IQueryable to death in the fact that it allows me to append to the query so I can get some fluent code for using it. But being able to do something like that seems to add more responsibility on the controller/BLL.
So what do you think? In the case of web applications would you be ok with trading off some performance for maintainable/cleaner code? Do you think it’s with to prematurely try to optimize everything you can? Because as we’ve seen you cannot predict all requirements.
1 Answer