The hottest Systems Design Substack posts right now

And their main takeaways
Category
Top Technology Topics

Composition is a function of communication

Tech and Thoughts • 0 implied HN points • 24 Oct 23
🕹 Technology Systems Design
  1. Communication is key for building software. Systems work best when they have clear and simple ways for different parts to talk to each other.
  2. Just like on the internet, software should focus on how parts interact, not just what those parts do. This makes it easier to adapt and grow.
  3. When designing software, spend time planning how components will communicate. Get this right early on to avoid problems later.

Prefer Composition over Inheritance

Better Engineers • 0 implied HN points • 23 Mar 23
🕹 Technology Systems Design
  1. Composition is often better than inheritance because it allows you to create new classes by combining existing ones. This helps avoid complex class hierarchies.
  2. Using interfaces can help you achieve different behaviors without relying on a single inheritance path. This keeps your code flexible and clear.
  3. Delegation lets you pass tasks to other objects, which helps separate functionality and maintain cleaner, more understandable code.

Adaptive Defense: Redefining Security for a Dynamic World

Phoenix Substack • 0 implied HN points • 20 Feb 25
🕹 Technology Systems Design
  1. Static security is outdated. We need systems that can adapt quickly to changing threats.
  2. Trust in security should be flexible. Instead of seeing things as secure or vulnerable, we should continuously assess and improve our defenses.
  3. Effective security must understand each situation. It's about using real-time information to respond appropriately, not applying the same rules everywhere.

The Tacit Ceiling of AI Knowledge Synthesis

Front Left • 0 implied HN points • 02 Mar 26
🕹 Technology Systems Design
  1. Document synthesis hits a tacit ceiling because written sources mainly capture explicit knowledge, not the judgment and intuition experts use, so skills built from them often fail on edge cases and novel situations.
  2. Extraordinary quality requires extracting structural rationale and conceptual models — decision principles like “When X, do Y, because Z” — and using a Decision Skeleton that links triggers, choices, failure modes, and boundaries to turn knowledge into reliable actions.
  3. Pipeline safeguards (compression guards, critical-distinctions registries, adversarial tests, and iterative passes) improve results but can’t fully solve selection or recover tacit knowledge, so external domain expertise and objective validation remain necessary.

There are two systems. Which one are you working on?

Bad Software Advice • 0 implied HN points • 25 Mar 26
🕹 Technology Systems Design
  1. You work on more than just the technical code — the system includes users, support, competitors, and the market, and missing that context can make your work irrelevant, wrongly specified, or badly prioritized.
  2. AI is lowering the cost of development, so developers are shifting from hand-coding everything to managing tools and judging agent outputs, which requires higher-level skills beyond writing code.
  3. Spend time learning the greater system and move up the stack; understanding users, support, and market forces helps you build the right thing and make better tradeoffs.
Get a weekly roundup of the best Substack posts, by hacker news affinity: