2 ms·
Yes, great, now you've complicated the workflow. What if the service fails to run? Or fails to pick up the changes? Now you've got another thing to think about.
by AnIdiotOnTheNet 7y ago
Yes, great, now you've complicated the workflow. What if the service fails to run? Or fails to pick up the changes? Now you've got another thing to think about.
Is the overengineering so ingrained in the average HN user that they cannot see why someone might not bother with that?
- danaris 7y agoIn the everyday active workflow—the actions the author actually has to take each time—it doesn't add any complication. It merely adds complexity in the processing, which is certainly something worth considering. However, in a case like this, the alternative—as we can already see—is to add complexity for every single reader on the front-end. So there's not really a perfect solution here—either the author or the reader has to deal with some complexity.