tl;dr:“My takeaway is that, when you get the chance to be faced with an opportunity that could get you in the “fast growth” zone, it’s very important to focus and make the most of it. Projects that can challenge you this much do not always appear, so when they do and you are in the right place to handle them it’s a great opportunity.”
tl;dr:“I like it when running a production system is boring. No outages, no hotfixes, no on-call duties… no problems. It might sound unachievable, but there are steps you can take to get closer to this state. One approach to get there I really like is being defensive with my code.”
tl;dr:“When I started managing the engineering department at my company, I wanted to have an interesting team meeting involving the entire team. My objective at the time was to set up a meeting that people would look forward to, going beyond simple team & company updates. It’s now been a few years since the first, and while not all presentations are a complete success, I’m pretty happy with the way it turned out.” Marc discusses the meeting format.
tl;dr:“As a manager, doing one on one meetings with your direct reports is your most important tool. I’ve talked a bit before about opening lines, but I figured it could be interesting to dig into how I handle this every week with my teams. I think it’s important to have a clear format shared to direct reports. This frames the conversation and helps the manager fullfil the objective, while giving some insights to the direct report regarding what this is all about.”
tl;dr:Failures are valuable to teams if looked on the right way. They can allow for "blameless retrospectives, more psychological safety for all and a quicker adoption of best practices through sharing experience."