Category Archives: design

Oxite Review

Several folks, including Microsoft employees and members of the Oxite team, have politely requested I do a post or few on the problems I see with Oxite and why I previously recommended that it is not a good example/sample from … Continue reading 

| 19 Comments

SystemTime versus ISystemClock – dependencies revisited

Yes, it’s true, I’m a big fan of the Dependency Inversion Principle and Dependency Injection.  Scandalous!  But there are some situations where DI can make your classes…rather interesting. In one recent example, we needed to model an Occupation.  A person … Continue reading 

| 8 Comments

Internal DSL Pattern: Nested Function

This is a portion of a larger set of posts on the subject of Internal DSLs. Nested Function is a pattern explained by Martin Fowler as part of his DSL book work in progress. Fowler’s take on Nested Functions is … Continue reading 

| Leave a comment

Internal DSL Pattern: Method Chaining

This is a portion of a larger set of posts on the subject of Internal DSLs. Method Chaining is a pattern explained by Martin Fowler as part of his DSL book work in progress. Fowler’s take on Method Chaining is … Continue reading 

| 2 Comments

ALT.NET Workshops: Internal DSL Draft Outline, Notes

I’ve been preparing for the upcoming ALT.NET Workshop (associated with KaizenConf) on Internal Domain Specific Languages (DSL).  The schedule hasn’t been released yet, but I’m pretty sure the Internal DSL workshop will be on Friday 31-OCT (don’t quote me just … Continue reading 

| Leave a comment

NotImplementedException and the Interface Segregation Principle

This week, Derrick Bailey will be in town (Austin) to talk about the SOLID principles.  One of the hardest ones to talk about, and find examples for, is the Interface Segregation Principle.  The ISP states: CLIENTS SHOULD NOT BE FORCED … Continue reading 

| 7 Comments

Request for Help: Need better guidance for beginners

This morning I happened to see the article “.NET Coding Standard & Code Review Points” linked from the good folks over at DotNetKicks.com.  I was horrified to see some of the very bad guidance being offered here. While I appreciate … Continue reading 

| 31 Comments

On good design and defining success

This is for the most part a reaction to conversations on design: Testability in .Net Design and Testability Good Design is not Subjective Believe it or not, I largely agree with all of these posts.  The conversation originally started around … Continue reading 

| 2 Comments

Good Design is not Subjective

In case you haven’t guessed by my recent flurry of posts, I’ve been engaged in some debates in the past few days about design philosophies and why some designs are “good” and some are “bad.”  I’ve been met with some … Continue reading 

| 28 Comments

Let’s try it again… testability succinctly

My last try wasn’t that successful, so I’ll try it again: (In-language based) Testability is the residue of a good design.* Better? * (This is a slight play on John Milton’s famous quote ‘Luck is the residue of design’) Post … Continue reading 

| 1 Comment