Developer mind

“OH HAI! The process to perform incremental testing is taking several minutes per iteration. This sucks! Automate this!”

“Automation totally rocks! The process to perform incremental testing is now only about a minute.”

[some period of time lapses]

“OH HAI! The process to perform incremental testing is taking a whole minute per iteration. This sucks! Tune the test harness!”

“Automation tuning totally rocks! The process to perform incremental testing is now a mere 30 seconds!”

[some period of time lapses]

“OH HAI! The process to perform incremental testing is taking a whole half a minute per iteration. This sucks!”

[…]

Lesson: If left to my own devices, I’ll spend more time tuning the testing process than developing the code being tested because it feels more wasteful to do otherwise.

Why thin clients will always lose in the end

Test run of my repos modification script: < 10 seconds

“Live” run of my repos modification script: > 10 minutes

The difference? Tests are done on a local clone and the live run is done against a server sitting out on the WAN.

You should have seen how long it took when I was doing iterative checks over the network instead of capturing the output of a giant svn ls operation.

The good news being, it all works so I can go home now!