Software Architect and Top Dawg
I mostly link blog as I let smarter people than I solve problems then I copy them to solve my own. I also post random things I run into the course of my day.
This post aims to dissect the power that exists in the Aggregate LINQ operator. I have realized that most programmers use it sparingly and have decided to put a couple of examples to clarify how you can use the Aggregate operator to perform a few tricks.
The author makes the assertion that the Aggregate operator is a bit confusing and rarely used. In my case, I know she's right. Good post to intro this guy to using Aggregates.
In the previous post of the Introduction to the Reactive Framework series, we covered how to create new IObservable<T> instances, either from scratch or from existing sequences. What this allowed us to do was turn an operation which was previously interactive, such as iterating over a collection, to a reactive, where I could have multiple listeners reacting to the same collection concurrently. This has nice implications for allowing us to scale our application in interesting ways. This time, let’s take another angle on making asynchronous programming easier.
Just more IObservable goodness. Though, I'm not sure I like the way the ending LINQ statement looks.
I guess a more Clean Code way would be to hide some of the subqueries behind methods.
Comments [0]
Something I should have referenced months ago that a co-worker pointed out to me. Finally, I can get organized samples and understand related items without fumbling through Reflector and the code docs.
I know, I'm way behind on this one
Comments [0]
Comments [0]