Change

I started this blog as a software developer to try to broaden my reach a bit and maybe get better jobs. I’m still a software developer privately and assisting with other people’s projects.

However, over the past 1.5 years I’ve transitioned to being a developer of people who develop software. This has turned out to be harder, longer, more difficult to predict and more rewarding. This has been a significant change.

When I started writing this post I was working at notonthehighstreet.com. In the past month I've moved to MOO, a brand I've admired, and been a customer of, for years. This is another significant change, not just to a new culture and a new location but also away from the world of apps, my domain of knowledge, to a team whose technical stack I understand in the macro- but not the micro-level.
This is because my focus is to instantiate change by developing the people who make the thing and not the thing itself. 

There is no debugger for people. You cannot run the same situation past them over and over again and log their responses to the console. There are some allegories with software in the development of people and teams, and I'm going to work to share some of those here.