Stupid Question 54: Performance, when should you care?
Performance, when should you care?
Performance seems to be the major subject this week for me as I’ve had daily discussion regarding performance on a new project I’m involved in at work. But, performance seems generally to be a popular subject and many of the questions on the blog have ended up being performance discussions.
So I have a biggie to ask. When should a programmer care about performance?
I tend to choose what I consider to be performance wise better if the amount of labor and memory footprint involved is the same while trying to keep down the number of dependencies for the
project. I do the basic stuff in regards to performance, but it isn’t a deciding factor most of the time (I’m not talking about database performance here, that is another story). If I know performance can be a big time issue for an application, I spend more time on that early on, but I do tend to tweak later if it an issue as I learned that you shouldn’t optimize early.
BUT, is that right? Do you optimize early, or tweak later?
Last modified on 2012-09-28