4 ms·
Poor choices during development reveal themselves in many ways: poor performance, awkward workflows, mandatory upgrades, one-way data conversions, inaccurate do
by FroshKiller 2y ago
Poor choices during development reveal themselves in many ways: poor performance, awkward workflows, mandatory upgrades, one-way data conversions, inaccurate documentation, and so on.
- pif 2y ago> Poor choices during development reveal themselves in many ways: ... All the examples you provided miss the point. Revenues are the point; all the rest is ancillary at best.
- FroshKiller 2y agoI'm not sure what you mean. jagged-chisel asked how we look for smart choices in the software we download and install. I gave examples of how poor choices manifest for end users, the idea being that a lack of those issues suggests smart choices. I don't see how revenue is relevant to the question. Revenue for whom? And how did my examples miss the point exactly?
- lelanthran 2y ago> Poor choices during development reveal themselves in many ways: poor performance, awkward workflows, mandatory upgrades, one-way data conversions, inaccurate documentation, and so on. Not necessarily. Some otherwise good systems might have one bug in each of those categories. And, most other poorly designed and poorly executed systems just chug along fine without the customer realising anything.
- stouset 2y agoSure, fine, a well-designed system can have bugs and a giant ball of duct tape and twine can work great. That's not the norm though and I hope we can all acknowledge that.