This is the first time in my career that I’ve left a company I really liked, which was quite a strange experience. I wanted to share some of the things I’ve learned along the way. I hope to turn many of these into full blog posts, so consider this the bitesize version.
As software engineers, sometimes we need to release significant code changes. And sometimes, we have to do it in a ‘big bang’. I’ve seen a few of these, both in an enterprise context (with weekend-long cutovers managed by teams of 20) and more recently at GoCardless. Here are some things I’ve learned along the way.
Earlier this year, we overhauled our permissions system at GoCardless. It’s given us a platform to build exciting tooling, as well as increasing our confidence and visibility of the system. This post shares some of the thought processes and lessons learned.
Autonomy and collaboration are two buzzwords in engineering management, and rightly so; they are both critical in developing and scaling a high-performing product team. As your organisation grows, more collaboration is required and teams feel their autonomy slipping away from them. Contracts is a simple concept which can help ease the tension, giving teams autonomy while maintaining a coherent strategy.
As you grow a codebase, eventually (or perhaps quite quickly) certain parts become ‘scary’. This blog post talks about why that happens, and some steps you can take to reduce the fear factor.
subscribe via RSS