The Handbook
The Hacker's Handbook is the essay archive of HappiHacking. It collects notes on BEAM systems, architecture, runtime behavior, technical leadership, and production work.
Some posts are polished essays. Others are field notes, old project memories, course fragments, or strange little maps of how systems behave under pressure.
Or follow via RSS feed.
Latest Posts
More essays
Staff, Not Author
How I use AI for my books
From Markdown to Print
One source pipeline that produces both PDF and ebook.
The Words You Do Not Have
In 1987 English made me faster and stupider in the same week. Last month a reader caught it happening to my novel.
Why I Wrote a Tech Thriller
The hacking was never the unrealistic part
When Exports Become Accidental APIs
Visibility domains and architectural drift on the BEAM
Archive
2026
The Shared State of Isolation.
Why Systems Collapse Under Load (and How to Fix It)
Your Code Has No Memory
From code change to intent, there and back again
Why I Built a Course on the BEAM
Understanding the runtime changes how you build on it.
2025
Observers: The Watchful Gnomes of the Village
Processes that watch, restart, and enforce lifetimes
Gatekeepers: The Traffic Controllers of the Gnome Village
Processes that protect the system from the outside world, and from itself
Routers: Processes That Only Decide Where Stuff Goes
The Gnome Village Mailmen
Resource Owners: One Process, One Piece of State
The boring, reliable center of most good systems
Workers: Do One Job, Then Get Out of the Way
Short-lived processes, polite pools, and where people overcomplicate things
Process Archetypes: The Roles in the Gnome Village
Every process has a job. Problems start when it has two.
Gnomes, Domains, and Flows: Putting It Together
From checklist to a running payments path
Flows Keep Work Moving
Design data, message, process, and call paths on purpose
Domains Own Code and Data
Keep modules, OTP apps, and state in the same lane
Gnomes, Domains, and Flows
Why boundaries decide whether the village holds
Supervisors Are Managers
Build a village of gnomes, not a park of machines.
The Gnome Village
Threads fight. Gnomes cooperate.
Exposing the 'Multibank Crypto Poker' Recruitment Scam
If it looks too good to be true, it is
Exactly once
Exactly once
Assembler, Stepper Motors, and a Hotel Pool
Revisiting the animatronic spy drama of Haparanda Stadshotell, three decades later
Why I Wrote the BEAM Book
Post-mortems, coffee, and a decade of stubborn curiosity
Your Finance Stack Is Lying to You
Accidental Complexity in Fintech
AI Rubber Ducking: When Your Duck Starts Talking Back
Debugging with an AI duck that asks questions back
The BEAM Book Is Almost Done. Here's What Writing It Taught Me.
Reflections on scope, clarity, and the joys of letting go.
Why Some Fintechs Scale Seamlessly; and Others Crash and Burn
Most fintech backends break under pressure. Yours doesn't have to.
Summon Your AI Sidekick: Building a Tireless Personal Coach
When Your AI Coach is Named Orrin
The Best Issue Ever Reported on GitHub
This one's a feature, definitely not a bug
Hyperchains: Your Own L1 with Aeternity Tech
Set Your Own Fees, Scale Without Limits
Synchronous vs. Asynchronous: Clearing the Confusion
Messaging, APIs, RPC, and Other Buzzwords Explained
RabbitMQ Reliability: A Reality Check
Reliability depends on topology, guarantees, and operations.
Forget Microservices: Just Use Erlang.
A distributed system, without the distributed headaches.
The Hidden Cost of Bad Payment Architecture
Because 'It Works' Is Not the Same as 'It Works Well'
Opinions: Just the Facts, 11 Years Later
Still no opinions. Mostly.
Microservices Are NOT an Excuse for Chaos
How Overcomplicating Your Architecture Can Destroy Scalability Instead of Enabling It
2024
Why Windows 11 Virtual Desktop Switching Is Slow
And How to Fix It
Developer Productivity for Early-Career Engineers
A course note for newer developers
Developer Productivity for Experienced Engineers
A course note for senior developers
Developer Productivity
Notes on attention, workflow, and engineering habits
Enhancing Fintech Security with Erlang
Build Scalable and Reliable Fintech Systems with Erlang
How Erlang Powers High-Volume Finance
Build Scalable and Reliable Fintech Systems with Erlang
TIPS and RIX-Inst: Navigating the Future of Real-Time Payments in the EU
Opportunities and Challenges for Fintech Companies
Developer Types
Addressing the Elephant in the Room
The Quest for Enhanced Productivity in Software Development
A Reflection One and a Half Decades Later
Designing Concurrent Systems on the BEAM
Principles and Strategies for Robust System Design
2023
Three Decades with Erlang
A Personal Odyssey
Recovering from a Hacked Social Media Account
A Quick Guide
Dev Containers Part 2: Setup, the devcontainer CLI & Emacs
Bring Your Emacs Friends to the Party
Dev Containers: Consistency in Development
Finding Freedom in Confinement
Seamless Productivity with Mouse without Borders
A Happi Hacker's Dream
Neural Networks in Elixir
A beginners guide
AI Laser Metal Cutting - Part 3
Replacing humans by AI optimization as a service
AI Laser Metal Cutting - Part 2
Replacing humans by AI optimization as a service
AI Laser Metal Cutting - Part 1
Replacing humans by AI optimization as a service
Audits through Merkle Root Hashes
Blockchain - The good parts
It is never about technology - until it is
Then it is Erlang
Book Review "The Goal - A Process of Ongoing Improvement" by Eliyahu M. Goldratt and Jeff Cox
Unleashing the Power of the Theory of Constraints on Software Development
How We Designed FATE
A smart contract virtual machine for the æternity blockchain
Unleashing the Power of Erlang's BEAM
A case study with Delta Exchange
Rapid Prototyping
Building a production ready MVP in 3 months
Taming the Spaghetti Monster: The Birth of Kappa
Solving Codebase Complexity at Klarna with a Business Layers Strategy
The Happy Path Method
Start with the path that proves the system.
HappiHacking's Just in Time Development
An Agile Success Story with Klarna's Installment Plans