4 ms·
Nice discussion. I agree whole-heartedly, when it comes to full systems and programs. As in the article, when it comes to a simple plug-in to a system however,
by alexobenauer 15y ago
Nice discussion. I agree whole-heartedly, when it comes to full systems and programs. As in the article, when it comes to a simple plug-in to a system however, rewriting an entirely new version of an API just for the plugin was simply unnecessary.
- davesims 15y agoAgreed, YAGNI is just as important as SRP. That's good design too. But hopefully if you do eventually need an API, your design was good enough to allow easy interface extraction, etc.
- alexobenauer 15y agoAbsolutely; that's a fantastic point.
- hippich 15y agoIf your API is not flexible enough and require to write ad-hoc code - it is broken and require refactoring. I know this is not lines up with "customer want it now and do not care", but code do not magically become less broken because of it.
- alexobenauer 15y agoAPI of objects, not public-facing API. The internal API objects had to be re-written in a new language.