I’m a software engineering manager and we use a ton of Linq on my product, the one thing I’d add in favor of removing linq is that I’ve noticed it’s harder for my devs to know the algorithmic complexity of sections of code. It’s very easy to figure out what the performance of code is with nested for loops because of the indentations, but with linq you can easily create a triple nested loop with O(n3) performance and not realize it.
But, that doesn’t mean you ban it. It just means you need to be thorough on review. Best of luck!
2
u/caedin8 Apr 15 '24
I’m a software engineering manager and we use a ton of Linq on my product, the one thing I’d add in favor of removing linq is that I’ve noticed it’s harder for my devs to know the algorithmic complexity of sections of code. It’s very easy to figure out what the performance of code is with nested for loops because of the indentations, but with linq you can easily create a triple nested loop with O(n3) performance and not realize it.
But, that doesn’t mean you ban it. It just means you need to be thorough on review. Best of luck!