But you lose track of when and where things are getting executed. That is the curse of modern software development. But LINQ is minor offender here compared to

But you lose track of when and where things are getting executed. That is the curse of modern software development. But LINQ is minor offender here compared to some kinds of remoting, code reflects from endless xml configs wrapped in gazillion interfaces and some inventive orm-s. Sadly our tools have not kept up with the complexity that is external to the executing code. The debugger in the pre- inversion of control/bean injection days was almighty because you had all of the program state in front of you. A little known fact is that if you wrap Java/C# code in enough unit tests you get Haskell.