10 Comments
Mar 30Liked by Fran Soto

One of the best read this week! at least for me based on what I am going through. 100% escalation is not bad, if something is a company principle then there shouldn’t be exceptions.

Expand full comment

Interesting concept about the bar raising people. How do they find the time to do it? Or they have X% of the week dedicated to bar raising?

Great article Fran!

Expand full comment

Very cool, thanks for sharing Fran.

I liked the idea of the escalation not as an evil, but a tool in the belt. It makes it a more collaborative process.

I also only now just learned what the whole bar raiser thing meant. I've heard it talked about but now I get it 😄. Seems like a concept that should be implemented in more places

Expand full comment
Mar 24Liked by Fran Soto

Wish more engineers favored truth-seeking. I know, sometimes it's hard to reproduce an issue, and you're working on something else anyway, but the insights you gain from getting your hands dirty might uncover a lot more problems that need to be addressed than simply looking at the problem in isolation or by writing a simple reproducer test.

As for mechanisms, I've been advocating for automation for years now. For example, I've advocated for using custom Linter rules over people manually suggesting coding styles in PRs or PR templates over going back and forth multiple times because the author missed some key things in the description. Such automations do a big chunk of the work.

I'm happy you're growing immensely with the help of your company culture and the system you have in place for Amazon.

Great work, Fran!

Expand full comment

Great read, Fran! I’ve heard a few times the story with Jeff Bezos uncomfortable phone call and forget the details. For Amazon those focus on customer service and satisfaction. Nice breakdown.

Expand full comment