3 ms·
> against DIYing literally anything I get your feeling but I largely disagree: I’ve seen too many DYI mini-projects that implemented just enough and became too
by znpy 2y ago
> against DIYing literally anything
I get your feeling but I largely disagree: I’ve seen too many DYI mini-projects that implemented just enough and became too much important, and when they broke no one was around to fix that (the implementer had left a long ago and left scarce to no documentation at all).
The nice thing about using an off-the-shelf product is that usually either it comes with support or there’s some kind of community where you can go and ask for help).
There is this insidious cognitive bias in (software?) engineers to only consider the happy path when thinking about the consequences of their actions.
- kiitos 2y ago> I’ve seen too many DYI mini-projects that implemented just enough and became too much important, and when they broke no one was around to fix that (the implementer had left a long ago and left scarce to no documentation at all) Personally I have seen far more damage done by a reflexive rejection of NIH syndrome, than the costs you're describing here. I've generally found it much easier to maintain a bespoke system built around a narrow set of requirements, than a general purpose system applied too-eagerly.
- carbotaniuman 2y ago> There is this insidious cognitive bias in (software?) engineers to only consider the happy path when thinking about the consequences of their actions. This applies to buying off the shelf software (and other things) too. Vendor provided software is not immune from bugs or shortcomings or terrible vendors.