Austin Code Camp 2013 Review

It's been a couple of days since the Austin Code Camp 2013. It was a great turn out. Overall around 200 plus coders, eager to hear about the latest trends, attended.  Here are a few thoughts that I'd like to share regarding Austin Code Camp. more...

Comments

Post a Comment

Popular posts from this blog

Simple Example of Using Pipes with C#

Image
So I decided to dig into understanding how Asp.net works under the hood, out of curiosity.  In the articles that I found the authors described the architecture in lower level details.  One of the things that caught my eyes was the use of named Pipes as a means of inter-process communications by the architecture.   So I decided to dig into that portion a little bit deeper.  I discovered that the .Net framework has a namespace for named pipes and it's quite easy to use. 

I intend to demonstrate a small example that I cooked up rather quickly by setting up a named pipe server and then connecting a pipe client to it.  Before I do that, I want to say as a disclaimer that I don't know that this example demonstrates the best way to use pipes.  What it does do is show the most straightforward way to use them.  Also, before you use pipes you should consider using something else like WCF instead if you need well defined interfaces, as using pipes is pretty raw.   Being the type of perso…
Read more

Difference Between Adapter and Bridge Design Patterns

As I was preparing for an upcoming presentation on the topic of Design Patterns, I was studying through the different patterns and could not differentiate between the Bridge Pattern and the Adapter Pattern. Right off the bat both of those patterns fall into the category of structural patterns. Both of those patterns allow us to take advantage of the Liskov Substitution principle. Both patterns allow us to swap out implementations.

It seems that I am not alone in getting confused in the disctintion between these two patterns. A simple google search with the phrase "bridge and adapter pattern" returns quite a few results. Here is an article in code project that illustrates the difference to a certain degree.

What came to mind in trying to determine the pattern required is the forces at work. This something that Steve Tockey pointed out when determining what pattern to use. He said basically that an engineer does not wake up one day and say "I think I will build a suspension…
Read more

IoC Container Vs. Service Locator

I had a conversation over the weekend with one of my colleagues because I didn't understand the difference between an Inversion of Control (IoC) container and a Service Locator. After our twitter conversation, I had to go back and read the article by Martin Fowler on the topic. Although the article is dated, it provides some valuable information. That information along with my colleague's information clarified the difference.

The confusion was mostly because both tools provide similar services, both provide run time resolution of dependencies. Also when improperly used, an IoC container can be used in the same fashion as a Service Locator can- as was the case in one of my former projects.

Before I get going too far, let me explain what I mean when I say "run time resolution of dependencies". In order to write testable code in OO we have to write classes that are loosely coupled. No coupling at all would be optimal (for testability), but as any programmer knows, that is…
Read more