

- MAKEMKV SEGMENT MAP LEAN ON PETE HOW TO
- MAKEMKV SEGMENT MAP LEAN ON PETE SOFTWARE
- MAKEMKV SEGMENT MAP LEAN ON PETE CODE
Robert shares some of the finer details of the challenges they encountered when trying to build these macros and the panel gives their own personal verdict on the age old elixir question: to macro or not to macro. They discuss common pitfalls when first diving into macros and resources which help to avoid these mistakes. In this episode the panel talks to Robert Ellen and his experience with using macros in Elixir to get rid of some repetitive boilerplate code. Simon- ACM Turing award lectures | ACM Other Books.Simon- Joe's Blog - a non-linear personal web notebook.
MAKEMKV SEGMENT MAP LEAN ON PETE SOFTWARE
Simon - Joe Armstrong’s PHD Thesis - Making reliable distributed systems in the presence of software errors (PDF).Sascha- The Book You Wish Your Parents Had Read.Allen- Kubernetic - The Kubernetes Desktop Client.Allen- K9s - Manage Your Kubernetes Clusters In Style."How NOT to Measure Latency" by Gil Tene Picks Erlang Solutions - Scalable Distributed Technology.Keeping Up with the Fans: Scaling for Big Events at Whatnot, with Elixir and Phoenix.
MAKEMKV SEGMENT MAP LEAN ON PETE CODE
They also discuss pragmatism in the context of software development, and how we as software developers are not paid to write pretty code but to solve business problems, which might also mean to choose NOT to build on top of the BEAM, if circumstances demand it. The panel and him discuss the challenges in finding the relevant bottlenecks in non-trivial software systems - and BEAM applications in particular - and what options there are to fix those. In this episode Simon Zelazny joins the mix to talk about his experience in scaling an Elixir and Phython based service to meet a once-in-a-blue-moon demand scenario.


MAKEMKV SEGMENT MAP LEAN ON PETE HOW TO
Today on the show, Everett Griffiths shares his insights on how to approach documentation simply and effectively. Don’t let all your hard work go to waste because you failed to communicate what your software is or how to use it. Documentation might be bad because it is flat-out wrong (typos, references to an older version, etc.), but more often documentation is bad when it fails to tell us what we need to know. Adi- Reach out if you're hiring Elixir devs! Adi- Buy a punching bag for both workout/releasing frustrationīad documentation wastes time, costs real money, and makes developers unproductive.

