Archive of: software
With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.
(via Four Short Links)
This report on an IRIX OS release from 1993 shows that the more things change, the more things stay the same.
It’s full of great advice such as:
Aim for simplicity in design, not complexity. Make a few things work really well; don’t have 1000 flaky programs. Be willing to cut features; who’s going to be more pissed off: a customer who was promised a feature that doesn’t appear, or the same customer who gets the promised feature, and after months of struggling with it, discovers he can’t make it work?
And a few brilliant burns:
Marketing - Engineering Disconnect: “Marketing – where the rubber meets the sky.”
Erm, progress indicators shouldn’t look like buttons. Just saying Adobe, I know you have a lot on your plate right now, but come on. You used to be good at this.
I love the release notes for Panic’s new version of Transmit.