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. My feelings on meetings have changed over the years but the general advice from eight years ago still stays the same

Last week I was talking with a group of friends about what their “perfect workday” would be. A number of scenarios were discussed when one person said “an entire day filled with meetings”. I began asking them questions about why they felt this way and what their meetings entailed to try to get an understanding of why they would want an entire day of meetings.

After a brief conversation, I came to the conclusion that meetings are poisonous and should be removed from the social norm of the business world.

When I was getting started early on in my career I made a lot of mistakes. I was unhappy, working for people who didn’t respect me and I was lost. I was unsure as to whether or not I wanted to continue being a developer and for a while, I was unsure if I’d ever be able to make it. I was working my butt off and burning myself out for a company I didn’t believe in.
These are the four things I wish I had known when I was just starting out.

Welcome to Procrastinating Manager, the second site in the series. 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.