3 ms·
I'm sorry, as someone who works on a production operating system that a planet full of people use, I respectfully disagree - the hard part of systems programmin
by xpaulbettsx 16y ago
I'm sorry, as someone who works on a production operating system that a planet full of people use, I respectfully disagree - the hard part of systems programming is making sure the application API is 100% semantically correct, since it is written in stone once you release it - architecture and programming advice is absolutely for you if you're one of these people.
Running usability tests with real developers on your API is extremely important to understanding how understandable and straightforward your design is - if you're an OS or a platform component, you don't get a 2nd chance to design an API; you do it right the 1st time or you live with the consequences for years to come.
- jedbrown 16y agoyou don't get a 2nd chance to design an API I think that is exactly the author's point, at least if you think that the best way to get to the Right API is to "think about it really hard" instead of "write a bunch of crappy prototypes".
- fauigerzigerk 16y agoI'm not sure you necessarily disagree with the article. He argues against the "do the simplest thing that could possibly work" principle. He basically says, don't release code that isn't properly thought through if you do something that many others will depend on. You are saying something quite similar, but you stress the importance of running usability tests _before_ releasing code as thinking alone might not be enough. I agree with that, but it's not the same as saying ship the simplest thing that _could_ possibly work. Quite the contrary.