3 ms·
If the actual expectation of every piece of software published is that the author is responsible for every harebrained choice made with it, then nothing would e
by Icathian 6y ago
If the actual expectation of every piece of software published is that the author is responsible for every harebrained choice made with it, then nothing would ever get published. That simply isn't practical.
My responsibility is to meet whatever guarantees I make when I publish a tool, and to open source the code if I plan to stop maintaining it such that it no longer meets the original guarantees.
If you want to lay at my feet the consequences of everyone who chooses to use it, whether it's an individual dev or some executive mandating its use to their whole org, I think you need to reconsider your perspective.
- jacquesm 6y agoThe general attitude to software development is why we really should not be calling it software engineering. More like software plumbing. And even plumbers tend to carry liability insurance.
- Icathian 6y agoIf you have a plumber fix your toilet, and multiple years later it breaks, and you go to them expecting their insurance to pay out for a replacement, how do you think that conversation will go? If you hire an engineer to build you a bridge, and years later you are jealous that every other city has two-level bridges, do you imagine they will rebuild it for you for free? I don't understand how software is any different.