Bleeding HTTP status codes

Developing web services there is an anti-pattern that I often see slip through the cracks and that is when HTTP constructs bleed through abstraction layers.

Should bugs be user stories

One topic that seems to come up regularly when teams try to be adopt agile is how to deal with bugs. Since these teams typically give Scrum a try they feel the urge to get as many story points as possible so it is natural to wanting to give these bugs story points so you get some credit for them. IMHO that is a huge mistake.

Maturity model for service monitoring

Over the years I've encountered organizations and individuals that all have different levels of service monitoring maturity. I figured it was time to talk a little about these. And by monitoring I mean the things you look at to understand the health of a service. And I'm especially considering how good vs bad health is quickly determined.

Object Calisthenics and Domain Modeling

Several times before I've covered how object calisthenics can save you so naturally I'm happy to see yet another example. This time referenced to as domain modeling which is probably a better approach than talking about calisthenics since that is a work many of us have no idea what it means...

A Swede's guide to US health insurance

When I moved from Sweden to the US the scariest unknown was how health insurance worked. And I must say that it is mind boggling at times. In my six years in the US I have experienced three different approaches. The short version is that if you consider moving to the US, make sure you understand how your health insurance works!

Software Development in different cultures

I was listening to this podcast which is talking about how the culture at different software companies is different in different parts of the world. I found it extra intriguing to hear how foreigners perceived working in Scandinavia vs their home countries since I've done the opposite journey.

Thinking for Programmers

I was watching this great recording from last year on how programmers should think. It talks a lot about the importance of writing a specification for your code.

What to do with a caught exception

Some people like exceptions and some don't. Some people like them for exceptional things. Regardless of what type you are there is also a debate about what you do with that exception once you catch it.

These are not the abstractions you are looking for

People around me often hear me mumble things like "I think we are missing a level of abstraction here". This is something that often happens when I help people understand how to efficiently unit test a piece of code. But right before Christmas I was working in some code that perfectly highlighted that all abstractions are not equal.

The I have no idea what I'm testing anti-pattern.

It is no secret that I'm not a big fan of service locators in general, but even if you are a fan of those there is a pattern I really don't want to see in unit tests. I will call this the I-have-no-idea-what-I-am-testing-anti-pattern.