Archive for April, 2006

ASP.NET 2.0 Providers, source code released

April 17, 2006 Leave a comment
Check out the details from Scott’s blog. This should be useful for someone who wants to extend ASP.NET using the provider model.
Categories: Uncategorized

Notes on frequently used patterns

April 12, 2006 Leave a comment

Talking about Visitor Design Pattern

April 10, 2006 Leave a comment

 Prakash has blogged a set of links on visitor.


Visitor Design Pattern

My team had to develop a component using Visitor pattern. Since i have not gone thru this pattern for quite some time, i searched in GOOGLE and found some interesting links.
Visitor Defintion:
The visitor pattern allows you to define new, polymorphic operations on a class structure, without touching the source code for the classes themselves. Visitor lets you define a new operation without changing the classes of the elements on which it operates.
Useful Links on Visitor Pattern
Categories: Uncategorized

What is a good design

April 8, 2006 Leave a comment
In essence

Great designs:

  • Are easily modified by the people who most frequently work within them,
  • Easily support unexpected changes,
  • Are easy to modify and maintain,
  • and Prove their value by becoming steadily easier to modify over years of changes and upgrades.

The Source Code is the (Final) Design – Get your hands dirty. Follow your design down to the code.

Don’t Repeat Yourself.

Be Cohesive.


Clarify, Simplify, and Refine.

Fail Fast – TDD

Optimize from Measurements

A space to watch – NDepend

April 8, 2006 2 comments
A space to watch – NDepend
Categories: .NET Framework

SOA Q & As

April 8, 2006 1 comment
Categories: Architecture

70-529 – Late march

April 3, 2006 Leave a comment I guess this should be live. Should give a go at it i thought.
Let us see 😉
Categories: .NET Framework

TDD Discussions

April 3, 2006 Leave a comment
Jeremy summarizes the TDD discussions going on. Interesting read
My 2 cents
TDD is not a replacement for QA Testing. The earlier you find a bug the cheaper it is to fix it. This is probably a known fact. TDD is trying to identify issues when the codebase is with the developer (earlier in the cycle).
TDD is not a replacement for design. CRC cards are at a level of abstraction higher than the deisgn thoughts introduced by TDD.
TDD umbrella can include the Automated acceptance tests too. Rather than being a purist and stick to Unit Testing i like the concept of Programmer Tests and Customer tests used by the TDD in Microsoft .NET book (James and Alex). It is more pragmatic.