C# LINQ thoughts 

Tired: LINQ syntax is for baby devs that need SQL coddling syntax sugar, real devs use Fluent syntax

Wired: LINQ scope rules and let binding allow you to easily create monadic closures that are far harder to replicate in Fluent syntax. More than just sugar

Inspired: LINQ syntax is for queries with hair on their chest, Fluent syntax is for baby queries


C# LINQ thoughts 

Feared: Colleagues at multiple jobs found out quickly that if I break out the LINQ syntax, something amazing and horrible is happening and its surface level readability defies the frightening nature of it.

C# LINQ thoughts 

Though presumably my worst abuses of LINQ syntax are behind me*, it remains a tool that I love.

I was also proud that I proved I could do in LINQ what others could in hand tuned SQL.

*I don’t expect to have another job with quite the same insane amounts of cross-database queries and hopefully never have reason to build a “business rules” engine built on Expression<T> and an abuse of LINQ syntax as a way for Access users to write much more performant code in a “familiar way”.

C# LINQ thoughts 

(Really was quite proud of that LINQ rules engine monstrosity at the time, despite its ethically problematic reasons for existence. Sometimes I’m curious to see the code again, but it is probably best it stays locked away in the proprietary dungeon of the company I built that for.)

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!