With my 30 years of both open and closed source software development I can safely say that in the vast majority of cases if you're developing performance-first you're doing it wrong. Develop for correctness first, maintainability second, and performance ... somewhere about nine thousandth. The only time I've felt the urge to develop performance-first was when I was writing code that ran under CP/M and was bit-banging directly at an industrial controller. It really needed to not miss any messages coming from the large potentially explodey thing, lest the potentially explodey thing notice and expensively shut itself down to prevent said explosion.
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.
With my 30 years of both open and closed source software development I can safely say that in the vast majority of cases if you're developing performance-first you're doing it wrong. Develop for correctness first, maintainability second, and performance ... somewhere about nine thousandth. The only time I've felt the urge to develop performance-first was when I was writing code that ran under CP/M and was bit-banging directly at an industrial controller. It really needed to not miss any messages coming from the large potentially explodey thing, lest the potentially explodey thing notice and expensively shut itself down to prevent said explosion.