tl;dr:Over the last two years, we've seen a dramatic policy debate playing out on the feeds of LinkedIn: "WFH vs RTO". Nearly everyone has an opinion, and many of them are held strongly. Some are held based on data, some on personal preference, and many are based on personal experience. Nearly all of them, however, focus on the wrong part of the debate: it's not really about "WFH vs RTO", but about "async vs sync".
tl;dr:“There's a whole host of mistakes that companies often fall prey to with respect to those they have leading teams, and I thought it a good idea to collect them into one place, under the umbrella heading of "manager antipatterns”.”
tl;dr:“There's a whole host of mistakes that companies often fall prey to with respect to those they have leading teams, and I thought it a good idea to collect them into one place, under the umbrella heading of "manager antipatterns”.”
tl;dr:Engineers (and their managers) have spent much of the last forty years learning the various repercussions and implications of distributed systems. As an engineering manager, I've discovered that there is a remarkable similarity between distributed systems design and engineering organization design.
tl;dr:“Sometimes as part of writing these predictions, I take a look around the Internet with what other people are predicting, and let me tell you, the predictions for this upcoming year are off the hook. Autonomous robots. Human-computer brain augmentation. AI-generated AI creating new AI. If you ever saw it in a sci-fi movie, somebody out here on the Internet is predicting "this is the year”!”
tl;dr:Ted shares his answer to the following interview question: "You're the tech lead and your team is getting stretched thin. You decide to add resources but you can afford 1 senior full-stack developer or 2 junior full-stack devs. Which do you choose and why?"
tl;dr:“There's a whole host of mistakes that companies often fall prey to with respect to those they have leading teams, and I thought it a good idea to collect them into one place, under the umbrella heading of "manager antipatterns”.”
tl;dr:“There's a whole host of mistakes that companies often fall prey to with respect to those they have leading teams, and I thought it a good idea to collect them into one place, under the umbrella heading of "manager antipatterns”.”
tl;dr:Ted shares his answer to the following interview question: "You're the tech lead and your team is getting stretched thin. You decide to add resources but you can afford 1 senior full-stack developer or 2 junior full-stack devs. Which do you choose and why?"
tl;dr:Ted shares his answer to the following interview question: "You're the tech lead and your team is getting stretched thin. You decide to add resources but you can afford 1 senior full-stack developer or 2 junior full-stack devs. Which do you choose and why?"