Amazon is well known for prizing clear writing.

One well written design doc can save you *thousands* of wasted dev hours. And when you've shipped, you can better advocate for your team by writing up your achievements.

Writing is a career superpower. Here's a guide. OK this unexpectedly took off - image alts for accessibility

Tip 1
- Use less than 30 words per sentence
- Replace adjectives with data
- Eliminate weasel words
- Does your writing pass the "so what" test?
- Reply questions clearly: Only "yes", "no", a number, or "I don't know".

CODING_INTERVIEW_README.md 👇 1. CLARIFY

Many people jump straight into solving the problem. Take time to ask clarifying questions — some people intentionally underspecify as a way to catch you out.

The BIG reason you want to clarify: demonstrating clear communication skills. Every employer wants this 💁‍♂️

24 Standard Causes of Human Misjudgment, from buffettmungerwisdom.wordpress.com/2013/01/14/ful… 1. Not recognizing Incentives

"I think I’ve been in the top 5% of my
age cohort all my life in understanding the power of incentives, and all my life I’ve underestimated it."

Question from a reader: "I've just been hired to take over frontend for a really complex application. Feeling very overwhelmed right now trying to understand the codebase. I'm really stressed out since nobody else on the team does frontend."

What would you do? My thoughts 👇 First off - it sucks that your company put you in this position. Ideally you would have a mentor/buddy to guide you through onboarding.

But things often aren't ideal in real life. Shit happens. We grow most when we deal with shit happening. Someday you'll look back and laugh.