SEP Blog

We’re curious people by nature. And we love to teach others what we’ve learned. So explore our blog to gain fresh insights from our expertise in areas ranging from culture to AI.

SEP Named a Winning Company in the 2022 Powderkeg Unvalley Awards

There is some friction between agile methodologies and the desire for upfront formal requirements that has really been bugging me lately. I often find myself wanting to have my cake and eat it too: I want clear and final…
Read More

Changing Plans

There is some friction between agile methodologies and the desire for upfront formal requirements that has really been bugging me lately. I often find myself wanting to have my cake and eat it too: I want clear and final requirements, but I don’t want to be forced to design an entire system upfront and drown […]
Read More

Why should I care what my code looks like?

Someone said to me recently “I don’t care what the code looks like, as long as it works.” This offended me because I take pride in making my code look nice and easy to read. Plus it makes me happy to develop clean code. But why should you care? I was on a project that […]
Read More

Constraints Driven Development…my favorite line of code

This post is inspired by the recent blog battle topic “My favorite line(s) of code” and a recent line of code that I was, literally, Laughing-Out-Loud at. (I apologize for disturbing any of my neighboring SEPeers.) Not the kind of laughing where you are like “man, what were they thinking!?!”.  This was the kind of […]
Read More

My Favorite Line(s) of Code

Onwards to Round 2 in our current blog battle here at SEP. This time I’ve been asked to write about my favorite line(s) of code. Unfortunately, I don’t have some fancy Ruby, Haskell, or Clojure to dazzle you with. My recent tenure spent managing projects leaves me with little time to focus on the latest […]
Read More

Never implement INotifyPropertyChanged again

I hate every time I am working on something and I have to implement INotifyPropertyChanged.  My DRY-dey sense tingles*.*  Not only am I forced to not use auto-properties (1st DRY violation), I’m forced to fire the event in each setter (2nd DRY violation), and specify the name of the property that is getting set, inside […]
Read More

Teaching StructureMap About C# 4.0 Optional Parameters and Default Values

This week I ran into wanting to use C# 4.0 optional parameters, but wanted StructureMap (my IoC tool of choice) to respect the default value specified for those optional parameters. The Problem In this example, we’ll be pulling a command out of the container.  The important part is the optional constructor parameter (level), and it’s […]
Read More