Emmanuel Oyibo

I used to write about blackjack strategies and slot machine odds. Yeah, I was a casino writer. Not exactly what I dreamed of doing, but it paid the bills. I had this itch for tech the whole time that I couldn’t scratch. I’d bookmark programming tutorials, buy courses I never started, and tell myself “next week” every single week.

Eventually, I got tired of my own excuses. Started waking up at 5 AM to code before work. Failed at Python tutorials during lunch breaks. Broke my local environment so many times that I became an expert at fixing it. The casino content was paying my rent, but those stolen hours with the terminal were feeding something else.

The transition wasn’t some grand plan. It was more like slowly turning a ship. First, I wrote about online casino tech. Then payment processing. Then APIs. Before I knew it, I was deep in Docker documentation and arguing about the best way to explain Kubernetes to beginners. It turns out that if you can make casino bonuses make sense to newcomers, you can explain container orchestration, too.

Three years later, I’ve published over 100 technical guides for platforms like Baeldung, Cherry Servers, Vultr, and Signadot.

Still learning, still breaking things, still Googling basic Git commands sometimes. But now I get paid to figure out how stuff works and explain it to others. Honestly, whenever I help a developer avoid the confusion I go through, it feels like hitting a jackpot.

The casino writing days taught me one thing: the house always wins. In tech writing, I finally found a game where everyone can win.