This post hit right something I dissected in my last role. In short, I was revamping/enhancing a property insurance policy pricing system as the lead from the

This post hit right something I dissected in my last role. In short, I was revamping/enhancing a property insurance policy pricing system as the lead from the business side (i.e. portfolio manager/actuary). However, much of the development team was truly incapable of writing software in any useful way, so I inevitably dipped into C# and SQL to help diagnose issues as we (as a team) worked on the enhancements. My business coworker and I found something that remains funny to this day: code littered with references or attempts to use the .NET TPL library to make the platform do more things "in parallel," but without actual knowledge of using such a library in practice. Nothing worked in parallel! There were blockers all over the place! As someone else said, TPL might well have been a //TPL TO DO. We suspected that TPL was there as one of those "look what I can do" intrusions that received praise from more senior devs/mgmt. even if it never actually did what it was supposed to do.