CTOs want the ability to get prototypes built and out into production fast. Others preach the gospel of building things properly. How fast can you be? How much can you perpare before you hit the ice? And one you built and shipped that prototype, how can you get any kind of speed trying to maintain and evolve something where many corners were cut for speed?

How do we want things to work then? Having an algebra for things might be nice. A sprinkling of interface, things that break noisily, and nice toolboxes to work with structs are all discussed.

  • The gospel of building things properly
  • The key to speed on the ice
  • Before you hit the ice
  • Bare maps
  • Every step made sense
  • The original intent very easily gets lost
  • The curse of all software
  • Strive for maintainability
  • It must not sprawl
  • A little sprinkling of interface
  • At dawn, we roadmap
  • Things that break noisily
  • A quantity unitless
  • The simple case of HTTP