Generally speaking, I like my projects to have a code coverage check to ensure it has above a certain level of coverage. I usually set this quite high (typically 100%) so it’s actually a challenge and it enforces a good level of rigour.
Update, 2015-12-16 05:30
Recently, I have been writing an Angular package for managing authentication with UI-Router. As part of that, I needed to create a provider that consumed an authentication factory. However, as authentication, was outside of the scope of that project, I wanted to allow the developer to write their own authentication factory. This meant that my
$loginProvider had to inject a dependency who’s name would change.
For a lot of my projects, I like to use OpenShift. It’s fairly simple to set up and reasonably fast. But the main reason is that they offer a free plan for developers which is great. I had the website set up on
*.example.com and the API set up on
api.example.com - any subdomain that didn’t begin “api” went through to the website OpenShift account and these two accounts were totally independent, communicating over HTTP. So far, so
This article was written when this blog was hosted on GitHub. I’ve since moved it across to using Ghost. This is kept as it’s still useful, although I’m not using this setup any more.
Last month, my wife and I went on a fabulous cruise for our honeymoon. When meeting new people, eventually you get asked the inevitable question “so Simon, how do you earn a crust?” With the exception of the Cockney train driver who thought that a software engineer made sofas, pretty much everyone responded the same way - “I couldn’t do that, I’m not clever enough”.