“The underlying issue is that the technology or platform is not the root cause of the unacceptable productivity levels. It is the organisational culture of accepting low quality that is the cause. This cannot be helped by replacing the technology. The remedy is all about behaviour. “

http://community.ative.dk/blogs/ative/archive/2007/01/29/The-Waste-of-Defects-_2D00_-Bugs-are-Stop_2D00_the_2D00_Line-Issues.aspx 


ToDoComponent planningTask =
Plan.ToDo("Plan project X")
.StartingNow
.MustBeCompletedBy("2007.08.17")
.ClassifyAs("Public");
planningTask.Save();


Not what usually comes to mind when I think of DSLs, but it’s still interesting. The calendar components use a construct called a Fluent Interface, in which the methods on an object return an instance of the class they are defined in, allowing actions performed on an object to be chained, as in the example above.

This is a very useful construct that is used in frameworks such as Hibernate / NHibernate. I’ve never really thought about using fluent interfaces to create a sort of pseudo-DSL, and I’m not sure yet how useful this would be with the types of domain entities I write in my day job, but this has got me thinking.

public static void main()
{
Console.WriteLine(”Hello World!”);
}