Skip to main content

100 not out

My hundreth post on this blog.

Anyway....

My current project is coming to an end and its been interesting looking back at what has happened on it from a technical perspective. The most interesting thing for me is that I have had to invest some time in thinking how to scale the solution to grow with the demand the business expects to see. I've been following the High Scalability feed for a while but a post led to another blog which has really impressed me - Ricky Ho's "Pragmatic Programming Techniques".

In particular Ricky's recent post really chimed with me as I've struggled recently to try and capture, even formularise why I've make certain design decisions and found there wasn't really anything more than "instinct" that pushed agility into the design in certain areas and away from others. The post is a very good read and great summary of a Kent Beck talk he attended - well worth 10 minutes of your time. I'd have loved to been at that talk.

Looking at the post history on Rickys blog it almost mirrors the areas I have been looking at in the last year, Cloud, NOSQL, Memcached, Hadoop - some great information and intelligent writing that I enjoy following - keep it up Ricky! (PS: great blogger theme too!)

The other thing of interest is that I've kept a kind of log of ideas and thoughts about the development principles & team processes that have worked and sometimes not - I hope to compile these into a generic do's & don'ts list that could be applied to any project.

Comments

Popular posts from this blog

Walk-Thru: Using Wolfpack to automatically deploy and smoke test your system

First, some history... The advent of NuGet has revolutionised many many aspects of the .Net ecosystem; MyGet, Chocolatey & OctopusDeploy to name a few solutions building upon its success bring even more features to the table. I also spotted that NuGet could solve a problem I was having with my OSS System Monitoring software Wolfpack ; essentially this is a core application framework that uses plugins for extension ( Wolfpack Contrib ) but how to unify, standardise and streamline how these plugins are made available? NuGet to the rescue again - I wrapped the NuGet infrastructure (I deem NuGet to be so ubiquitous and stable that is has transcended into the software "infrastrucuture" hall of fame) with a new OSS project called Sidewinder . Sidewinder allows me to wrap all my little extension and plugins in NuGet packages and deploy them directly from the Wolfpack application - it even allows me to issue a new version of Wolfpack and have Wolfpack update itself, sweet huh

Configuration in .Net 2.0

11-Dec-2007 Update I've updated this post to fix the broken images and replaced them with inline text for the example xml and accompanying C# code. This post has been by far the most hit on this blog and along with the comments about the missing images I thought it was time to update it! Whilst recreating the examples below I zipped up the working source code and xml file and loaded this onto my Project Distributor site - please download it to get a full working custom configuration to play with! Just click on the CustomConfigExampleSource link on the right hand side, then the "Source" link to get the zip. We are in the process of converting our codebase to .Net 2.0. We've used Enterprise Library to great effect so decided that we should continue with this in the form of the Jan 2006 release which targets 2.0 and I've got the job of porting our Logging, Data Access etc wrappers to EntLib 2.0. ...And so far so good - the EntLib docs aren't bad and the migrati

Castle/Windsor schema enables Visual Studio intellisense

There has been a lot of noise recently about Inversion of Control (IoC) with .Net recently (stop sniggering at the back java guys!).... I've been using IoC via the Spring.NET framework for over 2 years now - it's a completely different approach to coding and once you get your head around it everything just falls into place and development is a real joy again. As I mention, Spring.NET is my framework of choice but a recent change in employer has seen me bump up against Castle/Windsor . First impressions are that I like it - it's not as powerful or feature rich as Spring but that's not always a bad thing! The one thing I did miss though was Visual Studio intellisense when editing the configurations - Spring has an online schema that can be associated with a Spring configuration. This got me thinking - if the VS intellisense can be hooked into that easily why not create one for Windsor configuration? So I did...you can download it from my new google code site here . Remem