← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 72
  1. When AI Writes the Code, Who Owns the Change?

    Coding agents can produce changes faster than a team can explain why those changes were authorized, how they were verified, and who accepted the risk of putting them into production.

  2. Architecture Amnesia

    Solar Frontiers is a strategy game I have been building.

  3. Staff, Not Author

    I procrastinate the way I have always procrastinated: instead of writing the book, I build tools that help me write the book.

  4. From Markdown to Print

    I write books in plain Markdown.

  5. The Words You Do Not Have

    A reader stopped on the fifth word of my novel and asked whether it had been translated from Swedish.

  6. Why I Wrote a Tech Thriller

    Every thriller has the scene.

  7. When Exports Become Accidental APIs

    The Problem Erlang gives a function two visibility states.

  8. The Shared State of Isolation.

    A recent essay, "The Isolation Trap", argues that Erlang's isolation model has structural limits: deadlocks from circular calls, unbounded mailboxes, and escape hatches like ETS.

  9. Your Code Has No Memory

    Many teams can answer what a piece of code does, but far fewer can explain why it exists, what constraint shaped it, which tradeoff led to it, and whether that reasoning still holds, and that gap matters more now because we produce and change code at a pa…

  10. The Late-Night Feeling of Wonder

    The Late-Night Feeling of Wonder In 1980 my ten years older sister started university and brought home a TI-58 programmable calculator.

  11. Why I Built a Course on the BEAM

    Why I Built a Course on the BEAM Programming languages shape how we think.

  12. Observers: The Watchful Gnomes of the Village

    Observers: The Watchful Gnomes of the Village Some gnomes in the village don’t build bridges, bake bread, or carry mail.

  13. Gatekeepers: The Traffic Controllers of the Gnome Village

    Gatekeepers: The Traffic Controllers of the Gnome Village In every gnome village you eventually discover a small, serious-looking gnome standing on a bridge, holding a sign.

  14. Routers: Processes That Only Decide Where Stuff Goes

    Routers: The Gnome Village Mailmen Routers are the mailmen of the gnome village.

  15. Resource Owners: One Process, One Piece of State

    The Gnome Who Guards the Chest of Gold In the gnome village, not every gnome runs around performing tasks.

  16. Workers: Do One Job, Then Get Out of the Way

    In the gnome village, a Worker is the simplest citizen you can have.

  17. Process Archetypes: The Roles in the Gnome Village

    Process Archetypes: The Roles in the Gnome Village The BEAM makes it easy to create thousands of processes.

  18. Gnomes, Domains, and Flows

    Glossary: Resource owner = the process that owns mutable state for a domain object.

  19. Domains Own Code and Data

    Glossary: Resource owner = the process that owns mutable state for a domain object.

  20. Flows Keep Work Moving

    Glossary: Resource owner = the process that owns mutable state for a domain object.

  21. Gnomes, Domains, and Flows: Putting It Together

    Glossary: Resource owner = the process that owns mutable state for a domain object.

  22. Supervisors Are Managers

    Build a Village of Gnomes, Not a Park of Machines In the last post, The Gnome Village, we explored how the BEAM turns concurrency into cooperation.

  23. The Gnome Village

    The Gnome Village I see some developers that arrive at the BEAM carrying mental luggage from object-oriented or sequential programming.

  24. Exposing the 'Multibank Crypto Poker' Recruitment Scam

    TL;DR Fake recruiters are pushing a malicious “crypto poker” codebase.

  25. Exactly once

    Why "Exactly Once" in Payments Is a Myth, and What Works Instead Payment systems live with retries.

  26. Assembler, Stepper Motors, and a Hotel Pool

    The Spy Dolls Under the Dance Floor “A dirty spy.”

  27. Why I Wrote the BEAM Book

    Why I wrote the Beam Book After ten years of keeping Klarna’s core system upright I know this: a 15 millisecond pause in the BEAM can stall millions of peak-shopping payments, trigger a 3 a.m.

  28. Your Finance Stack Is Lying to You

    Your Finance Stack Is Lying to You Why Untyped Data, Floats, and “Excel Thinking” Are Quietly Costing You Millions At a recent fintech conference, I was struck by how much engineering effort, across both startups and enterprises, is spent cleaning up avoi…

  29. AI Rubber Ducking: When Your Duck Starts Talking Back

    AI Rubber Ducking: When Your Duck Starts Talking Back We’ve all been there.

  30. The BEAM Book Is Almost Done. Here's What Writing It Taught Me.

    The Project Nears Completion I set out to document everything I knew about the BEAM, and to discover everything I didn't yet know.

  31. Why Some Fintechs Scale Seamlessly; and Others Crash and Burn

    Fintech is a ruthless game.

  32. Summon Your AI Sidekick: Building a Tireless Personal Coach

    Setting Up an AI-Powered Personal Coach Introduction Why do our ambitious goals often fizzle out by the third week?

  33. The Best Issue Ever Reported on GitHub

    Technical authors often brace themselves for GitHub issue notifications-each ping might herald a misplaced comma, a misunderstood explanation, or worse, a confusing typo deep within a critical code snippet.

  34. Hyperchains: Your Own L1 with Aeternity Tech

    Hyperchains: Your Own L1 Chain Hyperchains are here.

  35. Synchronous vs. Asynchronous: Clearing the Confusion

    Synchronous vs.

  36. RabbitMQ Reliability: A Reality Check

    RabbitMQ: The Undeserved Reputation There’s a common claim floating around that RabbitMQ is unreliable.

  37. Forget Microservices: Just Use Erlang.

    Forget Microservices: Just Use Erlang.

  38. The Hidden Cost of Bad Payment Architecture

    The Hidden Cost of Bad Payment Architecture If you've ever tried to fix a broken payment system, you know it's never just one thing.

  39. Opinions: Just the Facts, 11 Years Later

    Opinions: Just the Facts, 11 Years Later A decade ago, I wrote a blog post declaring my distaste for opinions.

  40. Microservices Are NOT an Excuse for Chaos

    Microservices Are NOT an Excuse for Chaos Too many teams think "microservices" means "no rules."

  41. Getting the hang of Rebar3

    Rebar3 is the standard build tool and package manager for the Erlang programming language.

  42. Why Windows 11 Virtual Desktop Switching Is Slow

    Why Windows 11 Virtual Desktop Switching Is Slow If switching between virtual desktops in Windows 11 feels slow, you're not alone.

  43. Developer Productivity

    Developer Productivity This post outlines the structure behind the paid developer productivity course: motivation, habits, time, workflow, collaboration, and tools.

  44. Developer Productivity for Experienced Engineers

    Developer Productivity for Experienced Engineers This post is an audience-specific note from the paid developer productivity course.

  45. Developer Productivity for Early-Career Engineers

    Developer Productivity for Early-Career Engineers This post is an audience-specific note from the paid developer productivity course.

  46. Dev Containers Part 3: UIDs and file ownership

    This is the third entry in a series of posts on devcontainers; the first entry is here.

  47. Enhancing Fintech Security with Erlang

    Enhancing Fintech Security with Erlang: Insights from HappiHacking As the former CTO of Klarna and the founder of HappiHacking and Kindio, I've spent years at the intersection of financial systems and security.

  48. How Erlang Powers High-Volume Finance

    Handling high-volume transactions efficiently is a must in fintech.

  49. In Europe, the way people pay for things is changing.

  50. Developer Types

    The prototyping Monkey is a bit sceptical because he got two managers instead of developers to take over his product...