Skip to content

Comment on Optimize for change not application performanceparent

Comments

Very true. I think the authors area settles more in the webdev area, where you can make releases multiple times per day.

Optimize for what best serves your purpose. If you have high team fluctuation, optimize for readability. If you develop a spacecraft, optimize for safety. If you ship audio gear, optimize for latency.

I fully agree with that.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.