Reading legacy code well is one of the most undertaught skills in software development. bitcrowd wrote a field guide that's exploring codebases like it's 1999, and that compares that with how modern day coding agents work. - and where they silently fail. Learn about the limitations of both worlds. The judgement is yours.
Artéa built an Elixir library for parsing ISO 20022 financial messages like camt.053 end-of-day bank statements. They share what makes the standard painful to work with, and how pattern matching and function clause dispatch handle the multi-version mess.
Where do you put your HTTP response validation in Elixir? Artur Plysiuk argues it belongs in (Tesla) middleware, not after the call. The reason: middleware can fail the request itself, so unexpected statuses and malformed data actually reach your telemetry.
Mob is a new framework for building native mobile apps with Elixir. It runs the BEAM directly on mobile via NIF, with native views and all logic in Elixir. The post shares the backstory, design choices, and how it draws from Phoenix, LiveView, and prior art.
Production bugs don’t arrive one at a time. Honeybadger groups similar errors into a single issue and lets you pause or ignore alerts in a single click. More signal. Less noise. ⚡ Sign up for your FREE developer account →
If you've only ever reached for ETS to count things across processes, Andrea Leopardi has two more options to consider: :atomics and :counters. He covers how each works, their guarantees, when to reach for which, and benchmarks both against ETS.
What's new in Erlang/OTP 29? Björn Gustavsson runs through the highlights: experimental native records, multi-valued comprehensions, assignment in comprehensions, a new is_integer/3 guard BIF, security improvements, and several new compiler warnings.
What if your processes could survive node failures and pick up exactly where they left off? Chris McCord introduces DurableServer. It extends the familiar GenServer with automatic state persistence and cluster coordination.
You'll be joining a team of engineers across Frontend, Backend, SRE and QA. We're organised into cross-functional development teams assigned to specific verticals. This role is open for several teams, and we will define the exact team that you will be joining during the interview process based on the business needs and your preferences. Regardless of the specific team, you will be working on building tools, APIs and integrations for one of our products.
