Marcus Wermuth
A collection of 5 posts
Before I worked in a remote team , I was a freelancer and never needed to collaborate with teams very much. The way I used my calendar back then was pretty basic; maybe a birthday here and there. But when I joined Buffer in 2015 that suddenly changed. The more I grew as an engineer and the more I leaned into leadership and ultimately transitioned into management , the more I noticed how essential cal
“Hackathons” are pretty common at tech companies. During these events, engineers and others collaborate on a project with a goal is to have a usable piece of software to demo after the event – and eventually ship to customers. It’s a fun challenge to do a hackathon when you’re a remote team , which is why we’re especially proud after having recently hosted our third. Through every iteration, we’ve tried to improve. And after this third edition, it feels like
The biggest difference between remote work and co-located offices is where work happens. According to our State of Remote Work survey for 2019, 84% of remote workers work from their home. That means that most of us work and live in the same place. This results in the biggest struggle remote workers have: Unplugging after work. In this post I’ll share the four biggest lessons I’ve learned on how to create rem
Communication is the most important tool we have when it comes to team work – especially in remote work . But as an engineer, in the past I’ve focused more on code than communication. Although I talked to people, my output was writing code and solving problems. So when I became a manager , I realized that I needed to listen a lot more. Learning to Listen Listening sounds so simple, right? Well, for me it
Almost two years ago, I fell into becoming a manager . In my past career, I never thought that this would happen. Most of my life I’ve been a maker: working as an engineer, solving technical problems and building apps, products, or just circuit boards. People management was a huge change. I learned a lot of things the hard way through trial and error, success and failure — but also by reading a lot [https://buffer.com/resources/how-to-read-more-a