4 ms·
In many cases, choosing libraries and frameworks is motivated by political/symbolical reasons, and might not even expected to have any technical benefits. At o
by yobbo 5y ago
In many cases, choosing libraries and frameworks is motivated by political/symbolical reasons, and might not even expected to have any technical benefits.
At one point choosing java enterprise was about signalling ambition and competence. Nowadays service architectures/cloud etc serve this role of "decorative" tech choices. These types of choices factor out responsibility (of end results) from individuals while expanding their "organizational footprints" and giving their CVs a fashion make-over. Those are the incentives.
There would need to be counter-incentives.
- nilshauk 5y agoI think one such counter-incentive could be, "whatever tech you choose you'll have to live with the consequences by owning maintenance and future development." However, in our fast-paced industry people can switch roles and jobs so quick that they'll never have to face the consequences of their tech-choices.
- yobbo 5y ago> "whatever tech you choose you'll have to live with the consequences by owning maintenance and future development." But this is not in the interest of "architects", "system owners" or "buyers". They want programmers to be replaceable, not stakeholders. To "architects", frameworks/libraries make programmers replaceable, and programmers need frameworks/libraries to be marketable.
- nilshauk 5y agoYeah that makes sense. And “nobody got fired for picking technology X from large company Y”, there’s also that type of thinking.