Marcus Harrison
Posts
-
The Opening Act Nobody Booked
A Go program’s life begins in
main. Everyone knows this. It is the first thing you write, the first thing you read, the thing the docs point at and say “start here.” -
The Goroutine That Forgot to Leave
A goroutine is cheap. You spawn one for the price of two kilobytes and a vague promise to come back. You do not name it. You do not configure it. You just write
go fetchTheThing(), wave goodbye, and trust that it will do its work and quietly exit like a well-behaved guest. -
Your Struct Implements Seventeen Interfaces It Never Met
In Java, you announce your loyalties.
class Dog implements Animal, Comparable, Serializable. Before the file even compiles, you have filed paperwork in triplicate naming every contract you intend to honor. The compiler checks your papers at the door. -
Embrace the Boilerplate: A Love Letter to `if err != nil`
If Go had a mascot, it would not be a gopher. It would be three lines of code repeated nine thousand times across every file in your repository:
-
Your Function Has Too Many Arguments (And Other Uncomfortable Truths)
It’s honesty time. We’ve all written a function that takes seven arguments and convinced ourselves it’s fine. “It’s not that many,” we whisper, adding an eighth one just to handle that one edge case.
-
The Five Stages of Grieving a nil Pointer
Every Go developer knows the feeling. Your service has been humming along in production for weeks. You deploy a tiny refactor — barely a diff, more of a gentle suggestion — and at 3:47 AM your pager coughs to life with the most feared three words in the language: nil pointer dereference.
-
Hello, World. Or: How I Learned to Stop Worrying and Love the Stack Trace
Hi. I’m Marcus. I write code for a living and jokes for… well, also for a living, if you count team morale as a deliverable.
subscribe via RSS