3 ms·
Those are some interesting stereotypes you've got there. Developers don't value their time?
by binarymax 11y ago
Those are some interesting stereotypes you've got there. Developers don't value their time?
- stefan_work 11y agoI've noticed this as well. Most developers will spend 40 hours building a wheel instead of offering to wire up a pre built solution that costs money.
- binarymax 11y agoI think there are different reasons why that may happen - perhaps a misconception of the problem space and what an off the shelf tool provides, or misestimation of implementation time vs learning time. I don't think it is appropriate to say that developers don't value their time and therefore need managers, as a blanket statement.
- oneJob 11y agoI can tell you exactly why I might fall into this stereotyped category. 1) The wheel is closed-source, and I do not trust the vendor with that component. Linkages to that upstream code/license might not be acceptable/cannot not be justified given the cost/headache of dealing with the transaction. 2) The wheel is open-source and the code is crap or the license incompatible. 3) The wheel is open source and I worry that the direction of the project is not compatible with my needs. It might be awesome for the moment, but given that the project can potentially deviate in a direction that won't work for the needed solution, linking my code to that upstream project doesn't make sense. If the project does end up going in a different direction, I must break my stride, drop what I'm working on, and go back to retrofit that particular solution.