A Witch’s Guide to Go: 3 Charms to Enchant Your Software
summary
Describes building Enen, a streaming event store with a custom Raft-replicated SQL-like DB that exposes deep behavior through a one-line Connect(DSN, readOnly) API, uses a read‑write mutex, on‑disk migrations, backups and pings to meet SLA guarantees. Explains Go’s error patterns making distributed tracing hard and notes a proposal for Telemetry. Chronicles evolving Python SDK choices — from on_event callbacks to async generators with decorators — and claims those empathy-driven APIs improved user comprehension.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:46Who is Dr Bilbro
- 2:40Who is John Osterhout
- 4:10Philosophy of Software Design
- 4:45CS 190 Software Design
- 5:50Information Hiding
- 7:03Code
- 8:26Shallow Interface
- 9:27Errors in Go
- 10:42Rewrite narratives
- 11:38Accessibility
- 12:07Code conforms to conventions
- 12:32Users are not using Go
- 13:01No channels in Python
- 13:48Asynchronous generators
- 14:04decorators
- 14:31gift
- 16:17outro
related talks
39mEvent Sourcing with Elixir
33mChanneling the Inner Complexity
48mEvent Sourcing - what could possibly go wrong?
43mEvent Sourcing dealing with an eventful past
01h 07mThe Well Tempered API
49mKeynote: How to sell Elixir (Again)
41mDesign (Failures) Case Study
48mJourneys with Maps, Riemann, http.async.client, Canon fodder