Sunny

← All weeks

What I’ve been reading (W2, 2023)

Asking better questions and the butter thesis

Ask/answer these questions to make your pronouncements more thoughtful and practical.

  • And then what happens? After we take this action, after you shut down that agency, eliminate that division or launch this new project, what will happen after that?
  • How will that work? What are the mechanics involved that don’t suspend the laws of physics or organizational behaviour that will support this new way forward?
  • Why? Can you explain, beyond your reality-suspending confidence, why the system will respond to your approach?

The Butter Thesis

  • “Butter” is the term we use to describe interactions & experiences that are just so smooth. Rich, easy, delicious. Hard to define formally, but you know it when you see it / feel it.
  • Building for butter means understanding that every step of the experience can be honed, smoothed and improved to the point that it’s so good you can’t take it. Butter is deceptively simple. A single ingredient that yet does so much.
  • On the consumer side, Butter means end-user experiences that are frictionless and joyful.
  • Butter can apply to dev tools, enterprise/b2b products, and consumer products: Stripe API, Twilio API, Airtable, Slack, Linear, and Duolingo — Tools that are just so simple and fun to use (and useful!) that you can’t help but use them.

Real-time sync at Linear

  • The most straightforward way to implement real-time sync is to load the entire app state and keep it up-to-date with real-time changes.
  • Clients have the vast majority of their workspace data stored locally. Hence page loads are all but eliminated. As a result, startup times are fast, filters work instantly, and there are no page loads.
  • Sync automatically generates API calls, creates transactions, applies them on the backend, handles conflicts and errors, reverts erroneous changes, and rebasing in-fight changes and offline capabilities.
  • To create a new feature as an engineer, you essentially render and modify local in-memory data structures to build new functionality. All the complexity of requests, conflicts, network errors and retries are handled by sync for free.
  • All UI code automatically re-renders when the data that they accessed updates. Whether the data changes come from the user or the network doesn’t matter. So you get multi-player for free, too.
  • Side note: Reducing the number of layers engineers have to work on dramatically improves the speed at which we can ship new functionality.

Useful logging practices

  • You should remember that logging is for the developers (make is helpful for every developer)
  • Whenever you write a log, you must choose the correct log level (use ERROR, WARNING, INFO, or DEBUG)
  • Pick the attributes that are the most important and valuable to log, the attributes that will help you debug the continuation of the flow.
  • Each log message in the system should be unique. You’ll be confused about seeing the same logs at different flows inside the service if you see specific services.

Niches are overrated

  • Not having a niche gives flexibility and the ability to pursue various interests and opportunities.
  • They are combining their unique psychology, interests, motivators, and evolving curiosity and know-how to drop into a mode of being that enables them to keep going.
  • Don’t find a niche, find a mode — find a mode where you can continue to be excited about what you are doing.
  • The only thing that matters at the beginning is to stay in the game and find your mode. The only thing that matters is energy, excitement, and motivation to keep going.