3 ms·
While one of the main points of the article seems to be "duck programming is bad because it circumvents proper workflows", I suspect you could also reverse it a
by overgard 15y ago
While one of the main points of the article seems to be "duck programming is bad because it circumvents proper workflows", I suspect you could also reverse it and say "people write duck programs to avoid terrible workflows"
Not to say you should avoid best practices; but I think a lot of these systems come into being because the overheard required to do a task becomes more cumbersome than the task itself.
- ArbitraryLimits 15y agoExactly. I have a colleague who worked on some part of the control software of the Space Shuttle code in the 70s and he tells me that at some point, NASA's management decided to freeze the source code so no more modifications to it were permitted (sensible, if it's done) but they still wanted to be able to change the behavior of the software. The inevitable result was that someone wrote their own DSL for patching the object files generated by the original source code directly.