|
Elixir Radar Newsletter Issue #349
|
|
|
|
|
|
|
Jack Gray shows how to create a simple checkout flow using Stripe Checkout and the Stripity Stripe library.
|
|
|
|
|
|
|
Elixir has a built-in solution to measure code coverage when you run your test suite. But, what if you wanted to know about the code coverage of your system running in production? Cloudys shows how you could do this using the Erlang cover module, a coverage analysis tool for Erlang.
|
|
|
|
|
|
|
When you change one file, Elixir may need to compile other files besides the one you changed. Sometimes that can take more than you'd like to. Tim Gent explains what's behind that, concepts like run-time VS compile time, compile-time dependencies, transitive compile-time dependencies and more.
|
|
|
|
|
AppSignal - Sponsor
|
|
In this post, we will show how code predictability plays a crucial role in a project's short and long-term health. We will use Elixir's built-in features for this, like the pipe operator, tuples, and with blocks.
|
|
|
|
|
|
|
There are some subtle ways to accidentally undermine LiveView’s ability to track changes, which could harm the UX of your app. The LiveView docs outline a couple of pitfalls in this regard. Rockwell Schrock explores these examples and a couple of others and demonstrates how to detect and resolve them.
|
|
|
|
|
|
|
Todd Resudek got inspired by the book "Algorithmns to Live By", and decided to share how to solve the Secretary Problem. The secretary problem demonstrates a scenario involving optimal stopping theory, the problem of choosing a time to take a particular action for the desired outcome. An interesting application of Elixir with some probability theory.
|
|
|
|
|
|
|
Yiming Chen gives an introduction to the Promox library. Why does it exist? What features does it provide? How does it differ from Mox and Mimic? Why should you pick Promox over Mox?
|
|
|
|
|
THREAD Research - Remote, United States / Orange County, CA, US
|
|
inVibe is a division of THREAD that helps healthcare organizations listen to their customers. In this full-stack role, you will be working with the product engineering team to build out features and own projects end-to-end. The ideal candidate is familiar with working with the PETAL stack.
|
|
|
|
|
DockYard - Remote, United States
|
|
DockYard is currently helping support a client in hiring a Staff Software Engineer. The Staff Engineer would work closely with the DockYard team to build new features, integrate with other internal systems, and create future development roadmaps. 8+ years of experience working across the stack, from database and backend services, to API design and frontend development.
|
|
|
|
|
Aug 30 - Sep 02, 2022 - Hybrid (Aurora, Colorado / Virtual)
|
|
|
|
|
Oct 06-07, 2022 - Virtual
|
|
|
|
|
Nov 03-04, 2022 - Hybrid (Mountain View / Virtual)
|
|
|
As always, thanks for reading Elixir Radar!
|
If you'd like to know how to support our work even more, you can check this. |
|
-- Hugo
|
|
|
|
|
