Changing Coders

Redshift Wireless hit a minor speed bump yesterday where we came to the conclusion that we needed to change the programmer working on our back end. This was not because they did not do good work, but because the circumstances of the programmer changed in the time when we hired him and now, meaning that he was being stretched in too many ways. I was concerned that if I did not take action to assist him reducing his workload that it would be a complete disaster when things eventually broke.

So, I had two choices – I could either make an orderly transition, or make a transition when I had customers screaming for features. In the end I decided that it was in our best interest to make the transition now, but to leave open the possibility of him returning at some point in the future.

We have chosen a new programming team – they actually quoted on another project which they will probably do, but I saw the value of using them in this project. This does mean that I now need to bring together all the development documentation so that the new programmer can come up to speed. But from what I have seen, they are young and eager. They are willing to use GitHub, and even better, have promised daily status emails.

That last feature by itself is probably a reason to hire them! Status emails twice a week is probably all I need, but daily is a bonus! I will see how they god, and now just need to arrange an on site meeting between them and another member of the Redshift Wireless team as an introduction