Tech Lead Handbook

Tech Lead Handbook — Consensus vs Consent

The What

The How

Ship it and iterate it later.

Ship it if no objections.

Request a second pair of eyes

Request reviews

Request sign-offs

Workflow changes

Architecture changes

🔴 Red Flags

  • Handball the duty to someone else
  • Overuse extract pair of eyes to avoid responsibility and commitment
  • Try to please everyone but get nothing done

📜 Tips

  • You can’t make everyone happy.
  • The purpose of communication is moving people to action

Refs

Software Engineer | Tech Lead | Engineering Manager jamiewen00.gitbook.io/tech-lead-handbook/

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Publish Streaming data into Aws S3 Datalake and Query it

What is PIN Authentication

Pytorch primer

Let’s Fork With GitHub

Day 4: Errors can be fun, too

READ/DOWNLOAD#% Modern Control Systems (13th Edition) FULL BOOK PDF & FULL AUDIOBOOK

Changes in Subscriptions

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jamie Wen

Jamie Wen

Software Engineer | Tech Lead | Engineering Manager jamiewen00.gitbook.io/tech-lead-handbook/

More from Medium

The Focus Shift from Individual Contributor to Engineering Manager

Part 1: Adopting Architecture Decision Records within your technology team

Process automation — the secret sauce for eClinical platforms

What are we going to do in the future?