Sunny

← All weeks

What I’ve been reading (W34, 2024)

Ask for advice, not permission · Toasts are usually a bad UX

–

  1. The strategy required to find a great opportunity (lots of saying yes and exploring widely) differs from the strategy required to make the most of a great opportunity (lots of saying no and remaining focused). James Clear
  2. Ask for advice, not permission. Asking for permission shifts responsibility onto others, making them cautious and potentially resentful. If things go wrong, they share the blame, creating more risk than reward.
  3. Toasts are usually a bad UX. They always show up far away from the user’s attention.
  4. Bug squash interviews are a fun way to assess engineers. You give them a codebase with a bug and ask them to figure it out. These interviews mirror real-world engineering challenges: diving into unfamiliar code, hunting down bugs, and fixing them. It’s a chance to show off their debugging skills and tool mastery.
  5. A compute idea to let the network decide where to run the code @ernest
  6. Bad programmers worry about the code. Good programmers worry about data structures and their relationships.
  7. Rewriting code — whether once or starting fresh each day — sharpens your problem-solving skills, leading to higher-quality solutions in less time by reinforcing patterns and improving clarity. You can break through anchoring biases and find faster, more efficient solutions by challenging conventional approaches with extreme deadlines (“gun to the head” heuristic). Algorithms we develop software by
  8. Some tactics to scale software @joy-ooo-back-on-18-nov @elliot a. Clean up the logs: Fix real errors and ignore the noise. Noisy logs hide real issues and slow things down. b. Reduce database load: Cache frequently requested data that doesn’t change. Even simple queries add up. c. Go async: Move tasks to queues. Keeps the UI responsive and sets up parallel processing. d. Make work retryable: Things will break. Make sure tasks can quickly be restarted. e. Shadow users: Find out what they care about. It’s probably not what you thought.
  9. Each Postgres server can host multiple databases, but all databases share the same Write-Ahead Log (WAL). This means a point-in-time recovery or rollback affects all databases on the server. To avoid issues, especially when different services manage separate databases, hosting them on different Postgres servers. (Qian Li) @ernest
  10. Estimating software development won’t work. When work is predictable, it becomes a product you buy, not build. The real work is unpredictable, and you can’t define it until you start. The solution? Forget estimates. Set a budget, stay flexible, and adapt as you go. That’s how you deliver great software on time. (Software estimates have never worked and never will)