Passed the AWS Certified Solutions Architect – Associate exam.

I'm checking out Polywork. Instead of posting a CV and calling it a day, Polywork wants context and color for the things you've worked on. I like that. Will it help me find my next role (I'm casually looking)? We'll see.

Hat tip to Ryan @ One Dog Solutions for the VIP invite. 

March 5 was my last day at LinkedIn as an engineering manager. I'm deeply grateful to have had the experience, and was blessed to manage such a talented team. Two months later, I reflected on some of the reasons I left in this post: https://www.linkedin.com/pulse/why-i-left-linkedin-brian-hart/

I wanted to share a lightly-edited email I sent to my team of software engineers a few years ago. This was at a point when we were struggling with an above-average number of operational issues, while still needing to deliver projects on time. Several new hires had arrived, so help was on the way, but they were still coming up to speed. Plus, we'd recently reorganized teams, but there was ambiguity about where the lines were between two teams I needed to try to clear up.

That post is here: https://www.linkedin.com/pulse/team-brian-hart/

Change Management can sometimes feel onerous sometimes, like management CYA, but it's an essential part of Site Up at a company like LinkedIn. Not only does it help prevent some problems from making it into production, it helps recover faster once they do. Here is a LinkedIn post about it: https://www.linkedin.com/pulse/ok-what-changed-brian-hart/

About a year after returning to LinkedIn -- this time in a management role -- I worked with our TPM team in Production Infra Engineering to try to formalize some of our work processes around agile methods. This is a post I wrote back then about our efforts: https://www.linkedin.com/pulse/hows-agile-going-brian-hart/