And... we’re back to our exciting series on how to structure engineering organizations! Our ultimate goal? To finally answer your kid’s FAQ: “Mommy, daddy, where do platform teams come from?” In episodes I and II we covered two fundamentalist approaches of how we could structure an engineering organization:

I have to apologize to you all. I had not anticipated the amount of sleepless nights and marital problems I would cause to many of you by leaving you hanging with a cliffhanger like that, last week. A few cleaned up responses: WHAT HAPPENS WHEN WE GO VERTICAL!? I NEED

“But we have a QA team, right. Why aren’t they writing the end-to-end tests for this?” “We have a mobile team, right? Why don’t they build the mobile version of this?” “We have a performance team, right. Why don’t they write the load tests for this?” Excellent

The bad guys are winning. People have lost all hope. Who could possibly still save the day? Some noise comes from the bushes. All of a sudden, an excessively muscular dude with a head band jumps out from the branches. He’s carrying a large machine gun, wearing belts of

“Zef, you keep talking about all these amazing management concepts. You are an inspiration to all. However, what I really want to know is how you apply your enlightened ideas to being a parent!” — Nobody, Ever Dear mister or miss “Ever” — if this is in fact your real name. I’