• Worker-led
  • Sortition-based decisions
  • Ultra-sustainable
  • Slow and methodological > fast and loose
  • Open Source

Deep Work



  1. Continuous metrics drive continuous improvement
  2. Don't blame, fix.
  3. Complexity can neither be created or destroyed
  4. Independence is mythical. Autonomy is something every adult needs.
  5. Observing is no substitute for doing
  6. Culture is what you celebrate. Rituals are the tools you use to shape culture.
  7. If it’s not worth spending the time to over-communicate your point, the feedback is probably not worth slowing down the discussion for.


Be an active listener

Tech Ethics

https://www.bloomberg.com/news/articles/2020-08-03/silicon-valley-didn-t-inherit-discrimination-but-replicated-it-anyway https://www.academia.edu/1975319/Missed_Connections_What_Search_Engines_Say_About_Women https://ainowinstitute.org/disabilitybiasai-2019.pdf https://venturebeat.com/2020/06/12/researchers-find-racial-discrimination-in-dynamic-pricing-algorithms-used-by-uber-lyft-and-others/ https://www.propublica.org/article/machine-bias-risk-assessments-in-criminal-sentencing https://www.propublica.org/article/machine-bias-risk-assessments-in-criminal-sentencing https://docs.google.com/document/d/1HlRUtRKD6WzcO7zx0eHQcwfStk3joGAqASV67zhEYxE/edit https://docs.google.com/document/d/1GKMeE7S5n4SfJJv_zxTZ1Dsxb0kBrQKxdUjZy3JECF4/edit https://techxplore.com/news/2020-07-machine-satisfaction-romantic-relationships.amp


  1. Don't make your code do too much.

  2. You can't fix code by staring at it.

  3. Write Everything Twice

  4. Always comment your abstractions

  5. Optimize for deletion

  6. Do you know what you call someone complaining about existing code being awful all the time? "Junior"

  7. Good devs: understand what users want, write good code & ship things on time, help others do their jobs well

  8. Seven habits of good developers: Good documentation, ship fast/get feedback, be language/tech agnostic, have coding standards, simple code > complex code, use self-describing function names in your code, have good communication skills.

  9. Practice Egoless Programming

    The Ten Commandments of Egoless Programming


  1. Helpful: Be friendly, be kind
  2. Accessible: Inability is a failure of our system
  3. Lasting: Useful tools, built to last
  4. Human: Amplify humanity
  5. Directed: Have an opinion
  6. Systematic: Think in systems
  7. Candid: Make decisions in the sunlight
  8. Prime: Make a good first impression
  9. Tolerant: Work, even in failure
  10. Predictable: Advocate for clarity

User powers > Power users - Make complex, important work easy to make your users feel like super heroes. Don't hide powerful features for just your "power users"


  1. Work that’s too fine, too early commits everyone to the wrong details. - ShapeUp
  2. Effective teams write less software, and writing less software enables teams to be more effective.



https://twitter.com/BrianNorgard/status/1099389629348769792 Great developers are raised, not hired

  1. Hire for attitude, mentor for talent.


  1. Write for yourself, edit for your reader
  2. Con-tent not Cont-ent


  1. Close the loop. Don't let connections fall off.


  1. A mentor will share their experiences with you to contribute to your knowledge base.
  2. A mentor will use their network to help you succeed to achieve your goals.


B.A.S.I.C Method for Learning


Small b blogging