Is premature optimization to evolve on slow machines?

We need to develop on a slow box, because it makes us optimize early.

Randall Hyde points out “Error premature optimization,” there are many misconceptions about the Hoar quote:

We must forget about little efficiency, say, about 97% of the time: premature optimization is the root of all evil.

In particular, even though cars today scream compared to those that were on Hoare day, this does not mean that optimization should be avoided. So my esteemed colleague has a point when he suggests that we should develop on boxes at a moderate pace? The idea is that performance bottlenecks are more annoying to a slow box, and therefore they can get attention.

+5
source share
9 answers

Slow computers won't help you find performance issues.

, db , /. , , 500 . , .

- " ", , , , , " , ". , , . , .

( ? -?), , , . , .

-, - " , , , ".

"": -)

+10

, , "" .

, , . , - , :

, , , , , , , , , .

, , . .

, - , , ( ) , . , , , .

+21

, , , , .

(, ), ( , ), , , .

- , , . , , , , . , ( , , ) .

, , , , .

+3

, , , , .

, , , , , . . "" .

.

, , , ( ).

, , ? .

.

+2

Codd, , !

+1

, Vista?:

, . ,

? ? , ?

, ( ) , . .

+1

, .

, .

0

, (, , , ).

, , , , . , , , , , , .

. - MCU - FLASH, RAM , . ( , eeprom) " ". RAM (128KiB). , 256 , .

, () . ( ). 1,6 istdo 2.8. . - - , - . , () .

0

. 12- , , 12 "" , "".

As your development cycle approaches "today", your development machines should approach the current "average" speed of your customers' mailboxes.

-1
source