Was this the first time using .NET for most of your devs? > LINQ supports interleaving DB operations with not-db operations This hasn't been the case since E

Was this the first time using .NET for most of your devs? > LINQ supports interleaving DB operations with not-db operations This hasn't been the case since EF Core 3.0, it will throw an exception if something can't be translated to prevent this problem. Prior to this (EF Core 2.2), a warning would be spat out if an in-memory operation occurs. Due to this, I assume this project was a number of years ago. > The logger would log the message and the affected class in different lines. The default logging format is unfortunate, although it can be made a single line in .NET 5 onwards. This issue would've been easily solved by using Serilog, swapping out the built-in logging with a few lines of code. I don't know the last time I encountered a .NET dev that wasn't at least aware of Serilog as an alternative.