Trivial Emacs Kits
summary
Argues for shipping small, opinionated Emacs configs so teams share files across team and reproduce keystrokes, not abstruse advice; recommends treating project initialization as a project init as crucible where a specific set of packages and bindings is chosen and tested. Uses Emacs and simple init files (Emacs Lisp) rather than heavy frameworks, reports that trading configs gets teams productive and that evidence from a 30- to 40-person project can drive default changes.
AI-written summary · about