Quote

Simplicity is prerequisite for reliability. Edsger W. Dijkstra

Figure

diagram / screenshot placeholder

HandsOn

Try it yourself

A violet-tinted callout for runnable, try-it content. Drop steps or a snippet here.

Diagram — Mermaid

flowchart LR
  A[Idea] --> B{Worth it?}
  B -- yes --> C[Write]
  B -- no --> D[Delete]
A small flow, rendered client-side and theme-aware

Diagram — from a file

classDiagram
  class Observer {
    <<interface>>
    +update(State s)
  }
  class Model {
    -State state
    -List~Observer~ observers
    +get() State
    +mutate(fn)
    +subscribe(Observer o)
  }
  class View {
    -Element root
    +render(State s)
    +bindAdd(cb)
  }
  class Controller {
    -Model model
    -View view
    +addTodo(text)
  }
  View ..|> Observer
  Model o-- "*" Observer : notifies
  Controller --> Model : commands
  Controller --> View : owns
  View --> Controller : intent
MVC structure, loaded from src/snippets/mvc/structure.mmd

Diagram — PlantUML

participant Reader participant Blog Reader -> Blog : request /en/articles/x Blog --> Reader : prerendered HTML
PlantUML sequence (rendered via plantuml.com, no bundled lib)

Math

Display math:

$$v_i^{\,runtime} = \frac{1}{w_i} \sum_{t} \Delta t$$

Inline math like \(E = mc^2\) sits in the line.

Table

A framed data table with a mono caption below, auto-prefixed with a table label. Columns can be right-aligned and set in mono; cells can carry yes/no pills. It follows the page theme (light/dark), unlike code and diagram blocks.

PolicyPick costFairnessReproducible
Round-robinO(1)equal slicesstochastic
Weighted vruntimeO(log n)by weightdeterministic
Priority heapO(log n)starvation-pronedeterministic
LotteryO(1)probabilisticstochastic
Scheduling policies compared by pick cost, fairness model and reproducibility.