There are a million blog posts on how to "pick up" a new language. Most of them feel like they were written by someone who never shipped code at 3AM with PagerDuty breathing down their neck. This is how I do it — battle-tested, DevOps-brained, and tuned for curiosity
I’ve written code in a lot of languages. ColdFusion, back when I didn’t know better. PHP when I needed a job. Ruby when I wanted to feel something. Go when I wanted things to work. A little Elixir for the poetry. Java when I had no choice. Python?
Because Sometimes You Need a Knife, Not a Blender The problem with most APIs? They’re built like salad bars: slow, bloated, and full of shit nobody touches. Everything modular, everything abstract, everything wrapped in something else like a birthday gift you didn’t ask for. What we need is
But I was just too busy living my life. In early May of that year, I packed up what little I had in Roanoke, Virginia, and moved to New York City to start over. And somehow, it worked. I think back often to those first few weeks — bombing interviews, scribbling