4 ms·
I agree in theory but not in practice. Most developers have no idea how to measure the performance of a software product either in code units, libraries, featur
by throwaway0asd 4y ago
I agree in theory but not in practice. Most developers have no idea how to measure the performance of a software product either in code units, libraries, features, or the product as a whole. Worse, they really have no idea what to measure. This is even after you’ve passed that tremendous hurdle that you need measurements not assumptions.
A large part of that is due to the immaturity of software as a profession relative to other professions. Measuring things takes tremendous effort and many developers don’t want to challenge their deeply held assumptions of how things work. Often when you present performance measures to developers they will invent an excuse to throw the data out if they don’t like the conclusion.
- ncmncm 4y agoIf performance matters, you hire the subset of programmers who do have an idea about performance, and who even get it right before measuring.
- djmips 4y agoSigh, this is true. Better training and better tools can help make obvious their mistakes but I don't know how to combat the dogma. I've often been shocked how almost superstitious developers are - you'd think developers would have a more scientific approach but they are just as likely to chase after ghosts than optimize what needs to be optimized.
- peteradio 4y agoWrap a timer around your tests, there that is measuring something!