Life has been a little hectic lately, and so I’ve not been able to write as much as I would like to have done. I’ve still got the series I was working on which needs the next post writing, and there are some things I’ve been working on which I’d like to cover as well. But for now I thought I’d write a quick update on what’s been going on, technically and personally.

I promised myself I wouldn’t post too often with rants about random stuff I come across, and I like to think I’ve done okay so far (even though some companies cough Microsoft cough give me ample opportunity).

But one thing I’ve come across a number of times over the years, and again recently, is how some people handle errors in their APIs.

Don’t trigger the crazy person

I’m not talking about people using a 400 response when maybe it should have been a 412, those might need discussion, but at least when I’m consuming the API, I know something is wrong. No, I’m talking about people who wrap up their errors in a success response!

Whilst I’m working on the first series I’ve been putting together for this site, I have also been working a small command-line tool to help me with creating gitignore files when I’ve had a few minutes to spare (which have been few and far between lately).

One of the features I worked on briefly this weekend was to add the ability to auto-detect the right templates based on the projects content. There are quite a lot of templates so I started out with the ones that are most useful to myself first. Hey, I’m writing it, so I get to be a little selfish 😉