Meet the Team

CoderOasis has been running since 2011. That's a long time for a developer blog to survive without turning into a content farm or getting acquired and gutted. The reason it's still here is a small group of people who care more about writing something useful than writing something that performs well on an algorithm.

This is that group.

Traven — Lead Author & Editor

My name's Traven. I've been the one running CoderOasis since 2011, and I'm the person behind most of what you read here.

The origin story is embarrassing and I'll own it: I was up at 2am on a school night watching Ghost in the Shell. I didn't understand half of it. The philosophy went over my head, the cyberpunk politics were abstract, but something about the intersection of humans and technology hit hard enough that I had to understand it better. That's what got me into this.

First language was Perl. ProBoards used it, I wanted to know how it worked, so I learned it. Then PHP. Then MySQL. Then JavaScript, which I watched grow from jQuery and AJAX tricks into full Node.js applications. I picked up TypeScript because a friend convinced me type safety was worth the overhead — they were right. I've written Python to improve a Discord bot codebase before leaving due to drama that had nothing to do with code.

On the professional side: Lead PHP Developer for three cybersecurity firms building custom solutions. Systems administrator for two hosting companies — SolidShellSecurity from 2010 to 2014, then VPSNode, which I owned from 2021 to 2023. I've built plugins and addons for XenForo, vBulletin, WordPress, and most of the major PHP web application platforms. I've done freelance cybersecurity auditing on servers, web applications, and full systems under my own brand, SudoSecurity.

That's the background. The result is a blog where I write about things I've actually done, tools I've actually used, and problems I've actually had to solve. When I get something wrong, I say so. When something is bad, I say that too.

CoderOasis isn't trying to be neutral. It's trying to be honest.

If you want to reach me directly, Architect members have a line. Everyone else can find me in the Discord or via the comments.

The Contributing Team

CoderOasis has always had a small circle of friends and collaborators who contribute when they can. These are people with their own technical backgrounds, their own areas of depth, and their own opinions — which is why the writing here doesn't read like it came from one voice trying to cover everything.

This section gets updated as people join the rotation. If you see a byline you don't recognize, check the author page on that post for their background.

What CoderOasis actually is

It's a developer blog. Not a media outlet. Not a startup. Not a content company with a growth team and an editorial calendar reviewed by legal.

The articles are long because the topics require it. The opinions are direct because hedged technical writing wastes everyone's time. The code examples are real because toy examples teach you toy things.

Since around 2003 or 2004, I've been writing code. Two decades of that produces opinions. CoderOasis is where those opinions go.

The topics have shifted over the years — more AI coverage now, more deep-dives on security incidents, more infrastructure content as self-hosting has become a real option for more people. But the approach hasn't changed: read the source code, run the thing yourself, understand why it works before you explain it.

Why membership matters

Running CoderOasis on a budget has always meant making tradeoffs. Time spent writing is time not spent on client work. Server costs are real. Tooling costs money.

Membership revenue is what lets us publish more, go deeper, and keep the site free of ad networks and affiliate link nonsense. Every paid member is directly funding the next article.

If you want to support that — the membership page has the options. If you just want to read — everything public stays public.

Thanks for being here.