Please don't do this and take this article down. As others have mentioned, the experiment is flawed.
Don't prematurely optimize. It can lead to a number of problems:
It becomes harder to read and understand
It can lead to future errors
Go after the big fish first. Find the performance bottlenecks first and fix those before worrying about the tiny things.
Don't complicate your code unless absolutely necessary. Follow the KISS principal.
I recently found myself reviewing code from a senior software engineer that was filled with premature optimizations. It was very hard to read and created an abundance of code for what purpose? Just to save a negligible amount of time - we're talking far less than a millisecond. Orders of magnitude less than your standard network delay.
Don't be that engineer.
Don't encourage others to be that engineer.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Please don't do this and take this article down. As others have mentioned, the experiment is flawed.
Don't prematurely optimize. It can lead to a number of problems:
Don't complicate your code unless absolutely necessary. Follow the KISS principal.
I recently found myself reviewing code from a senior software engineer that was filled with premature optimizations. It was very hard to read and created an abundance of code for what purpose? Just to save a negligible amount of time - we're talking far less than a millisecond. Orders of magnitude less than your standard network delay.
Don't be that engineer.
Don't encourage others to be that engineer.