// Topic

Programming

Definition

Programming coverage in this archive spans 3 posts from Mar 2018 to Feb 2021 and leans into practical engineering craft: interfaces, testing, and maintainable implementation details. The strongest adjacent threads are go, performance, and rust. Recurring title motifs include go, rust, services, and developer.

What the archive argues

  • The through-line is clarity first: simple designs that survive change beat clever abstractions.
  • The consistent theme from 2018 to 2021 is disciplined execution over hype cycles.
  • This topic repeatedly intersects with go, performance, and rust, so design choices here rarely stand alone.

Execution checklist

  • Keep interfaces small, automate regressions early, and make operational assumptions explicit in code.
  • Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
  • When boundary questions appear, cross-read go and performance before committing implementation details.

Common failure modes

  • Abstracting before usage patterns are stable enough to justify indirection.
  • Treating style consistency as optional until quality and velocity both degrade.
  • Applying guidance from 2018 to 2021 without revisiting assumptions as context changed.

Suggested reading path

References

3 posts