Reading this question I found this as (note the quotation marks) ‘code’ to solve the problem (that’s perl by the way).
100,{)..3%!'Fizz'*\5%!'Buzz'*+\or}%n* Obviously this is an intellectual example without real (I hope to never see that in real code in my life) implications but, when you have to make the choice, when do you sacrifice code readability for performance? Do you apply just common sense, do you do it always as a last resort? What are your strategies?
Edit: I’m sorry, seeing the answers I might have expressed the question badly (English is not my native language). I don’t mean performance vs readability only after you’ve written the code, I ask about before you write it as well. Sometimes you can foresee a performance improvement in the future by making some darker design or providing with some properties that will make your class darker. You may decide you will use multiple threads or just a single one because you expect the scalability that such threads may give you, even when that will make the code much more difficult to understand.
My process for situations where I think performance may be an issue:
Note that this does not apply to higher-level design decisions that are more difficult to change at a later stage.