Hacker News new | ask | show | jobs
by cjohnson318 1495 days ago
This idea comes up in painting. The rule of thumb is that it's done when there's nothing left to add; when adding the next thing does not provide much more value value than it costs in terms complexity.

With coding, it seems like it's much more difficult question to answer.

2 comments

With coding, I often find Antoine de Saint-Exupéry helping me to limit myself: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."
I feel like this quote is why I can't have a removable battery, a headphone jack and an sd card in a new phone.
Perhaps. I always assumed it had more to do with offering better waterproofing, but maybe that's naive.
Or maybe more to do with users buying more of a particular brand of Bluetooth headphones and not having an arbitrary and universal input (you can do a lot of crazy stuff with an audio jack see square).
I swam for three hours today with my stock iPhone taking incredible 4K video of our diving and surfing adventure.

that advanced waterproofing is awesome.

Wouldn't sea water be corrosive?
I suppose that might be one reading, though IMO the battery, jack, and card slot have just been replaced by more bells and whistles like more/fancier cameras, biometric sensors, NFC, and other gobbledygook that was more important to someone than being able to plug into the cassette adapter in my car. Not exactly what I think of when I hear "nothing left to take away."
Unlike a painting, software can be continually improved and enhanced after it's released.