2 ms·
Another aspect I didn't see mentioned was that, at least in my experience, one can put too much effort into solving a problem. Then one ends up with a nice besp
by magicalhippo 7y ago
Another aspect I didn't see mentioned was that, at least in my experience, one can put too much effort into solving a problem. Then one ends up with a nice bespoke solution, but once it's been used for a bit, the requirements change and the solution might end up being a poor fit.
Very often in my experience this is because the client doesn't have a perfect handle on what exactly it is they want, which is only natural when venturing into the unknown. So they end up spec'ing a solution that doesn't exactly match the ideal work flow.
These days at work, when the client wants some new custom feature, we try to figure out if we can get something good enough by making small adjustments to existing features.
Then, when the inevitable changes come, we're in a much better position to determine the true requirements if we decide to go for a bespoke solution.
This does however require that the code is malleable, so I write with that in mind.