Software

Information

  • What is map/reduce for, anyway? - Ayende continues on from his previous visual explanation of Map/Reduce with a look at some of the situations where the map/reduce pattern is applicable, and others where it is not
  • SubSonic Migrations Without SubSonic - Rob Conery talks about the changes made to SubSonic migrations, and why they aren’t included in SubSonic 3, showing how they have been moved into their own project and are now open to use by anyone regardless if they use SubSonic.
  • "The F# Survival Guide" - "…the first book you read in your F# journey…" - Greg Duncan highlights a great looking introduction to F# written by John Puopolo with Sandy Squires and available as a web based ebook, introducing the core concepts of F#.
  • Prism, A Look Ahead - The Patterns & Practices Client Team set out their plans for a Prism Version 4 release in September 2010, and talking about their testing and findings of running Prism 2.1 on .NET 4 / Silverlight 4 Release candidates.
  • Silverlight 4 + RIA Services - Ready for Business: Index - Brad Abrams kicks off an updated series of posts on Silverlight RIA applications updated for the Version 4 Release candidate. The linked post is the index, and so far 3 parts out of 15 have been completed.
  • Semantic Code: Migrating From A Chatty Interface To A Simple One With A Data Transfer Object - Derick Bailey takes a look at using a Data Transfer Object to change how you work with an interface which is ‘Chatty’ (requires lots of calls), and outlines why doing this can gi ve you significant advantages.
  • Introduction to the Reactive Extensions for JavaScript - Wikipedia Lookup - Matthew Podwysocki shares another example of the Reactive Extensions for JavaScript in operation, looking at using them to create an autocomplete example using Wikipedia as the datasouce.
  • Poll on Entity Framework 4 - one year on - Eric Nelson re-issues his Entity Framework 4 poll for 2010 to provide a comparison set of results against those provided in 2009 to see how far the platform as come in terms of knowledge and awareness.
  • Do not name a class the same as its namespace, Part Three - Eric Lippert shares the 3rd part in his series of posts on naming of classes in namespaces talking about the process of creating naming hierarchies and why we as humans do it, along with why having an interior node with the same name as a parent represents a failure of classification.