Hosting this page on Notion, as I expect this list will be updated semi-regularly.

On Product

• The Product-Minded Software Engineer, and why it is important to become one

• A short thread:

  https://twitter.com/GergelyOrosz/status/1513162635520495623?s=20&t=MblCziYcTTYwFR-md8GKYA

On Reading

• The Four Levels of Reading (fs.blog), the first instalment in a multi-part series on How to Read, which goes beyond reading to entertain into reading to understand. A key quote:

  The easiest way to improve our understanding is from people who understand more about the subject than we do.

On Decision Making

• The Work Required to Have an Opinion (fs.blog); hint: it’s a lot of work, but all required. Read, talk to experts and understand their position, follow any trains of thought that run counter to your own views and see things in multiple perspectives. A key quote:

  We all are learning, modifying, or destroying ideas all the time. Rapid destruction of your ideas when the time is right is one of the most valuable qualities you can acquire. You must force yourself to consider arguments on the other side. — Charlie Munger

On Code Reviews

• What You Should Look Out For When You Review Pull Request by Meng Taing, a modern, pragmatic, easily-accessible guide to reviewing PRs, with practical examples throughout
  • Also check out Meng’s related article, Pull Request Etiquette for Reviewers and Authors, where we learn why responsiveness (and replying to a PR in under an hour) is important
• What to Look for in a Code Review, a multi-part series from Upsource, including Tests, Performance, Data Structures, SOLID Principles, and Security

On Engineering Management

• The Qualities and Skills that separate an Engineering Manager, a Director of Engineering, and a VP of Engineering, by John Friend (one of the best Quora answers I’ve read in a while)