Musings of an Engineering Leader

Over the last ten years, I’ve built two (relatively) successful company engineering blogs. The first was at a travel company called G Adventures. We weren’t a tech company per se, but we solved a lot of cool engineering problems. Unfortunately this blog was abandoned after I left. The next was at Sentry. The scale of challenges was different than at G Adventures and I think the quality of posts show that....

Last year at the Sentry Toronto Office (ps, we’re always hiring!) we started a new tradition of presenting lightning talks in front of the office. A lightning talk can be on any topic you wish. Since we’re a tech company, some talks are technically focused but the only rule is that they’re less than 5 minutes. This helps people improve their presentation skills, work on talking in front of a large group and craft talks for conferences or other reasons in a safe place....

In 2022 I read 20 books. This was 8 more than the goal I set in 2021 and the second-lowest number of books I’ve read since I started keeping track back in 2018 (you can find the list here). I had originally set a goal of 12 books, a modest increase from the 9 that I read in 2021. A big reason for the increase was regaining a commute into the office in mid-2022 as well as a vacation without kids for the first time in several years....

I’ve been a big proponent of writing as a form of learning for many years. In University I wrote programming tutorials on https://devjargon.com with a friend. These old articles are now posted on here and you can see how poorly they were written. Next came https://procrastinatingdev.com (now redirects here) and a number of years I wrote about more in-depth technical articles. As my career progressed into management so did the topics I wrote on....

This question was recently asked in a local engineering slack organization and it got me thinking, what would the ideal amount of time spent on technical contributions be for me? When I first transitioned from a developer to a manager I didn’t know how I provided value. I assumed that being a manager was largely the same as being a developer except now I had to talk to other developers and help them become better somehow....

Most developers at one point or another in their careers have thought about switching to management. Maybe your boss left suddenly and you were the most senior engineer on the team. Maybe you’ve spent a number of years in your current role and are wanting a new challenge. Or, if you’re lucky, your mentor brought up some traits they thought would make you a really good manager. Whatever the reason, you’re here now, trying to figure out whether this is the right move for you....

For the better part of the last decade, I’ve been an Engineering Manager (EM) and Director of Engineering (DoE). I’ve learnt a number of ways that don’t work when it comes to leading people and a few ways that do and I’d like to share them with you. A few weeks ago one of my co-workers asked me what it was like getting into management. As I reflected on that question I realized it was one I’ve answered before....

In 2021 I read 9 books. This was 21 less than the goal I set in 2020 and the lowest number of books I’ve read since I started keeping track back in 2018 (you can find the list here). Some of this had to do with working remotely for the full year and losing out on 3 hours’ worth of reading time during my commute. Some of this had to do with burnout and honestly not having any energy left at the end of the day to read....

In 2020 I read 25 books. This was 5 less than the goal I set in 2019, but, as everyone knows, 2020 was a doozy. I often use my commute to read and with Covid happening, I started working from home which reduced my reading time significantly. In June I also switched companies which reduced the time I had to read even further. Overall I’m happy with the number of books that I finished, including some really good ones....

Eight years ago I wrote about how meetings are poisonous . At the time I was the senior developer on my team and I was getting pulled into 4-5 meetings a day. This killed my productivity and made it difficult to get any of my IC work done. I struggled for many months until I realized that I could just say no to meetings. Since then I’ve transitioned from developer to manager , manager to director and then back to manager....