> Software engineering is now a team sport. "Now" meaning since the 1960s (and probably before)? > See http://boringtechnology.club/ http://boringtechnology.c

> Software engineering is now a team sport. "Now" meaning since the 1960s (and probably before)? > See http://boringtechnology.club/ http://boringtechnology.club/ There are plenty of "weird" (in the sense of the parent comment) "boring" (in the sense of the essay you linked [1]) languages out there. Common Lisp and Erlang spring to mind. They are old technologies, and their capabilities and failure modes are well-understood. Maybe not by me and you and the average programmer off the street, but after decades of use, the knowledge is available. There's also an argument to be had about how much you should value the personal familiarity your team and the people you hire have with the technology. Certainly there's a cost to using unfamiliar technology, and there's a trade-off when choosing between an old, battle-tested, highly capable, but unfamiliar technology and something that is less capable but nearer to hand. [1] "the capabilities of these things are well understood. But more importantly, their failure modes are well understood" https://mcfunley.com/choose-boring-technology https://mcfunley.com/choose-boring-technology