3 ms·
Counter-argument: coming up with your own, carefully considered solutions to every technical challenge is absurdly time-consuming. The reason we can build such
by nippoo 6y ago
Counter-argument: coming up with your own, carefully considered solutions to every technical challenge is absurdly time-consuming. The reason we can build such complicated applications in such a small amount of time is partly because we're relying on other people to make default, sensible tradeoffs - a framework supporting a particular type of SQL database, or NoSQL, or PHP or Django or whatever it might be. The mental effort of analysing all the tradeoffs of doing something one particular way (with such a wide range of possible options) for every little decision rapidly gets overwhelming. Of course it's worth doing a bit of research (which often ends up being "read someone else's blog" for bigger decisions, but unless you're willing to spend 2 months building a prototype application in each of Ruby, Django, PHP, and whatever other fun new JS framework du jour there is, it's perfectly valid to go for the path of least resistance and hope it doesn't cause you too many problems in the long run.
- ori_b 6y ago> Counter-argument: coming up with your own, carefully considered solutions to every technical challenge is absurdly time-consuming. You should really understand the problem you're trying to solve. Once you understand the problem, evaluating a solution is not so hard. And implementing a solution without understanding it is negligence that will bite you in prod sooner or later. https://blog.nelhage.com/post/computers-can-be-understood/ https://blog.nelhage.com/post/computers-can-be-understood/
- quickthrower2 6y agoThere just isn’t time for what I think you are saying. Analysis is a cost itself. Shortcuts have to be taken to get anything done. Judgment is required to navigate those shortcuts. Some might be unknown unknowns.