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.LinksThe Scott - Amundsen race to the South poleAccelerate, by Nicole ForsgrenParse, don't validateMnesiaDeep modulesPure functionsPlugElmBruce TateCRC - Create reduce convertEctoRocHappy Path Programming. Episode 47 features Richard Feldman and RocRichard Feldman, creator of RocQuotesThe gospel of building things properlyThe key to speed on the iceBefore you hit the iceBare mapsEvery step made senseThe original intent very easily gets lostThe curse of all softwareStrive for maintainabilityIt must not sprawlA little sprinkling of interfaceAt dawn, we roadmapThings that break noisilyA quantity unitlessThe simple case of HTTP

Ver todos los episodios