{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Regular Programming","title":"About Developing Speed","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/8d60225b\"></iframe>","width":"100%","height":180,"duration":2286,"description":"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?\nHow 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.\n\nLinks\nThe Scott - Amundsen race to the South pole\nAccelerate, by Nicole Forsgren\nParse, don't validate\nMnesia\nDeep modules\nPure functions\nPlug\nElm\nBruce Tate\nCRC - Create reduce convert\nEcto\nRoc\nHappy Path Programming. Episode 47 features Richard Feldman and Roc\nRichard Feldman, creator of Roc\nQuotes\nThe gospel of building things properly\nThe key to speed on the ice\nBefore you hit the ice\nBare maps\nEvery step made sense\nThe original intent very easily gets lost\nThe curse of all software\nStrive for maintainability\nIt must not sprawl\nA little sprinkling of interface\nAt dawn, we roadmap\nThings that break noisily\nA quantity unitless\nThe simple case of HTTP","thumbnail_url":"https://img.transistorcdn.com/C_-AHQqsYbdliFKrXsdN7TWYO9_tZENNrKOb2TIA9xc/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzE5MjQ1LzE2MTg5/MzM2ODUtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}