4 ms·
> To cut things short, always use the easiest solution to solve a particular problem and once that solution does not work for the business anymore reassess what
by cjs_ac 1y ago
> To cut things short, always use the easiest solution to solve a particular problem and once that solution does not work for the business anymore reassess what the new requirements are and either try enhance the current solution or find an alternative that better solve the problem.
When solving a problem, solve the problem you have, not the problem you think you might have in the future, or the problem you wish you had. Your solution will prove inadequate in the future, but you are unlikely to correctly predict in what way your solution will be inadequate.
- f1shy 1y agoBut: if it is not more work, you can solve your problem by solving a family of problems around your problem in the problem space, making the solution robust, as small changes in the problem definition can easily be catached by small changes in your solution. That should, with no extra work, solve future problems.
- nashashmi 1y agoI think you are saying you should be structured well enough to change your system to solve future problems. Like do you really need a dashboard on day 1? Or reports on day 2? Sometimes you just need a log of data. And the columns can grow and shrink.
- chii 1y ago> you are unlikely to correctly predict in what way your solution will be inadequate but you can choose a current solution that does not block nor inhibit a future solution. As they say, always keep your options open, and don't vendor lock-in yourself into a corner.
- t_mann 1y ago> Your solution will prove inadequate in the future, but you are unlikely to correctly predict in what way your solution will be inadequate. One inadequacy could be complete dependency on a vendor who accidentally locks you out of all your services or starts scalping you with ever higher fees. That one is quite predictable here.