Other People's Content

This is a list of selected articles and talks I’ve enjoyed and that which I aim to read or watch, listed in alphabetical order.

already read

• Amy Hoy
  • How the Blogs Broke the Web
• Anders Hejlsberg, Bill Venners, Bruce Eckel
  • The Trouble with Checked Exceptions
• Andreas Klinger
  • How I think about Code Management
• André Staltz
  • Unidirectional User Interface Architectures
  • Why we need Callbags
  • Your IDE as a presentation tool
• Anne-Laure Le Cunff
  • Mindframing: a personal growth framework
• asthasr
  • asthasr.github.io/posts/danger-of-simplicity
• Brent Jackson
  • Interoperability
  • Iterations on a Theme
  • The Design Graph
  • The Three Tenets of Styled System
  • Themeability
  • Two Steps Forward, One Step Back
    • 🖕 Fuck naming shit when you don’t have to.
    •  ⊃ Use a (superset of CSS) in JS, not a subset.
    • 🦖 Don't settle for CSS methologies from 2013.
• Cory House
  • The 7 Pillar Developer: A holistic approach to building an exceptional career
• Dan Abramov
  • Goodbye, Clean Code
  • My Decade in Review

    Dan started early and worked super hard. A humbling and motivating read.

  • Preparing for a Tech Talk, Part 1: Motivation
  • Preparing for a Tech Talk, Part 2: What, Why, and How
  • Preparing for a Tech Talk, Part 3: Content

    Need an algorithm to improve your tech talks? This is it.

    It helped me immensely.

  • TODO comments Twitter thread

    TODO doesn’t mean you actually intend to do something. It’s a marker for the next person that the logic was left unfinished...

    TODO comments are good.

    I believe that honesty is the essential quality of a software engineer. Whenever I have a vague idea of how to fix/improve something but no time to do it, I'll leave a todo. Whenever I do a hack, I'll admit it in the comment, explain why it's bad and what problems we should expect.

    It wasn't obvious to me when I learned to program. "My code doesn't need comments." -- I thought. Clean code is final. It is supposed to be beautiful, almost perfect, right? It grew on me with time, while working with deadlines, clients, project managers, and legacy code.

    Code Review comments perish. They have to be searched for. They can be lost while migrating between version control systems or VCS hosting services. Conversations on Slack or JIRA tickets are even more ephemeral. TODO comments are immortal. The memory of them will survive in your git history.

  • The Wet Codebase
  • overreacted.io/fix-like-no-ones-watching
• Ehsan Noursalehi
  • Why Do We Interface?
• Eric Sink
  • Act Your Age

    Eric Sink writes about the chasm between Early Adopters and Pragmatists and describes a Pragmatist in Pain needed to sponsor your product across this chasm.

• Gregory Ciotti
  • Easy Reading Is Damn Hard Writing
• Henrik Kniberg
  • Making sense of MVP and why I prefer Earliest Testable/Usable/Lovable

    MVP and misconceptions around it, filled with delightful illustrations and real-life examples.

• Jani Eväkallio
  • Foam: One Month In 🛁
  • onChange
• Joel Hooks
  • Badass: Making Users Awesome by Kathy Sierra
  • Digital Garden
  • Stop Giving af and Start Writing More
• John Otander
  • JSX as a design tool data structure
  • Styling themes
• Justin Meiners
  • Think in Math
• Kent C. Dodds
  • AHA Programming
  • Colocation
• Kevin Mahoney
  • http://kevinmahoney.co.uk/articles/tests-vs-types
• Lars Kappert
  • github.com/webpro/programming-principles
• Martin Fowler
  • martinfowler.com/bliki/BeckDesignRules.html
• Matt Biilmann
  • To WWW or not WWW
• Rich Hickey
  • Maybe Not
  • Simplicity Matters
• Scott Wlaschin
  • Domain Modeling Made Functional
• Sezgi Ulucam
  • A deep-dive into Relay, the friendly & opinionated GraphQL client
• Sibelius Seraphini
  • What should you Build next?
• Steve Yegge
  • The Nonesuch Beast
• swyx
  • Big L Notation: Modeling Rates of Learning
  • Eponymous Laws
  • How I Approach First Principles Thinking via Logic and Epistemology
  • Learn in Public

    This is lifechanging. I recommend it even to non-developer friends.

  • css-tricks.com/types-or-tests-why-not-both
  • www.swyx.io/writing/learning-gears
• Tanya Reilly
  • Being Glue
• Ted Kaminski
  • Deconstructing the "Unix philosophy"
• Tom Critchlow
  • Building a Digital Garden

    I encountered this in Joel Hooks's Digital Garden.

    I love the paragraph about stock and flow. The stock — high-quality, long-lasting content — is something I aspire to accumulate here. Tim got me hooked on nurturing my own digital garden. This page is one way to do it — a reference point for conversations with friends. After I write some more articles, I'm going to add a table of contents and highlight my favorite work.

  • Small b blogging
• Tomasz Łakomy
  • tlakomy.com/who-is-senior-developer
• Umer Mansoor
  • Write Less Code
• Vyacheslav Egorov
  • How the Grinch stole array.length access

    mraleph has a lot of good pieces on V8 and JS optimization. This is one of them.

  • Shaky diagramming

    This is 🔥.

future reading

• Angus Croll
  • If Hemingway Wrote JavaScript
• Benjamin C. Pierce
  • Types and Programming Languages
• Dominic Betts, Grigori Melnik, Fernando Simonazzi, Julián Domínguez, Mani Subramanian
  • Exploring CQRS and Event Sourcing
• Harold Abelson, Gerald Jay Sussman, Julie Sussman
  • Structure and Interpretation of Computer Programs

    I have some bad memories with the last textbook I've read (Cormen's Introduction to Algorithms), but I've heard a lot of good reviews of SICP.

• many authors? (Conaw?)
  • Roam White Paper