Something i came across while i was developing a framework for one of my clients. Source : Brian Button's Blog Brian’s Handy Dandy Rules for Framework Development Clients come before frameworks Ease of use trumps ease of implementation Quality, Quality, Quality Be an enabler It’s a people problem 1. Clients come before frameworks This was easily the most commonly heard bit of advice my poll revealed, and it matches up very nicely with my own experiences. The best frameworks are not

Awesome personal web site of Bruce J Mack here . You can find a alot of templates and information on MSF, and Microsoft Best Practices and Design Patterns. Good work Bruce!

The chapter meeting for September was a blast in Malaysia which I was luckily able to make it to. Check out the details @ http://malaysia.iasahome.org

Finally I managed to make it for the IASA Executive meeting at Genting, Malaysia, and boy was it awesome… Apart from the wonderful weather and excellent hospitality of the members of IASA Malaysia and Microsoft Malaysia, it was a pleasure knowing so many wonderful people who foster community spirit and give a damn about it... I met many council members of IASA Malaysia who are really passionate about community spirit. It goes to show that the very word 'community' is much more than running a forum

More of my notes on Udi Dahan 's podcast on - Does SOA requires ESB? Does SOA require ESB? A single system that will be divided by autonomous services. Autonomous services as opposed to simple services, that a lot of the industry is talking about, add another layer of richness into what goes into a service and what a service’s behavior is. If we were to take a concrete example of what the difference between a simple service and an autonomous services is, an example of simple service would be something

Just to share some notes I took from Udi Dahan 's excellent podcast - Does SOA mean the end of OO? Why did we need SOA in the first place? And what are we using OO for? Both of them are attacking the problem of software development – OO from bottom up and SOA from top down. Let’s start looking at OO design of a given application. OO was started in the single process era – a single process in a single application on a single thread on a single machine. If you are building a single app, SOA probably

Finally http://blogs.msdn.com/gianpaolo/archive/2006/05/30/610611.aspx

We're in the midst of establishing the Singapore chapter of IASA, and tomorrow is the key members gathering to discuss some of the crucial issus like the constitution. The Singapore IASA chapter is located here (Please excuse us, for the site is not fully functional yet). For those who do not know about IASA, its an international community of Software Architects with many chapters all around the world; you can read more about the Association here . We've managed to secure some of the most prominent

An interesting conversation sparked up today when I was together with my users assisting them for UAT. UAT. User Acceptance Test. It's a norm that is inserted in all software development lifecycles. It's a part of software development. To us in Info Tech, UAT is something we don’t really give a second thought to. We learnt it in our schools, we've seen our seniors prepare for it when we started our careers, we've heard our colleagues talk about it. There is nothing special about it - to us it has

Awesome stuff - The TechEd Architect contest for those who are attending TechEd this year... Wish I was there...