2 ms·

I think I've kinda protected myself from that by working across multiple operating systems and different stacks. I think a lot of devs would do well to try diff

I think I've kinda protected myself from that by working across multiple operating systems and different stacks. I think a lot of devs would do well to try different frameworks, different ways of programming (myself included). I think EF might get a bad rap because it's pretty closely tied to MS SQL Server - and if you don't know exactly what you're doing it will write some pretty hideous queries for you.

tracker1 6y ago
Should give Dapper a try, much cleaner imho... Though one of the projects I'm on is no abstraction at all.. most of the calls are via sprocs and using JSON for data input/output from the db directly. edit: by no abstraction, we have like 4 db methods that have a different generic type interface, but that's it across hundreds of different SP calls at the API later.