Systems builder. IT professional. Christian. Technology is not just what I do — it's how I understand the world.
I'm Gershom James — a systems builder and IT professional with over seven years of hands-on experience across networking, cybersecurity, cloud infrastructure, and Linux environments. I care deeply about how things work, how they break, and how to make them better.
My relationship with technology isn't a career move. It's genuine fascination — the kind that keeps me up late troubleshooting a network issue not because I have to, but because I need to understand what's happening at the packet level. I didn't grow up wanting a job in IT. I grew up wanting to know how everything fit together, and technology turned out to be the most honest place to ask that question.
"Whatsoever thy hand findeth to do, do it with thy might."
— Ecclesiastes 9:10 (KJV)
I'm a Seventh-day Adventist Christian, and my faith isn't separate from my work — it's the foundation underneath it. I believe in stewardship, discipline, and craftsmanship as biblical principles, not just professional ones. When I build a system, I'm accountable for it. When I secure a network, I'm protecting real people. When I write code, I'm creating something that should reflect the order and care of a Creator who doesn't cut corners.
Scripture informs how I think about technology. Proverbs 3:5-6 — "Trust in the Lord with all thine heart; and lean not unto thine own understanding" — reminds me that technical confidence without humility is arrogance. Colossians 3:23 — "Whatsoever ye do, do it heartily, as to the Lord, and not unto men" — sets the standard for every system I touch, whether anyone else sees it or not.
My path in technology has been a steady, deliberate climb — not a sprint. I started with the fundamentals and never stopped going deeper.
I self-host almost everything — not because it's easier, but because understanding your dependencies is the most underrated form of digital freedom. When something breaks, I know exactly where to look.
Tools change. The instinct to ask "how would this break?" is permanent. Years of security work trained my eye for patterns — in a network, in a system, in a problem — before they become incidents.
GUIs hide complexity. The terminal demands you understand what you're doing. That's not elitism — it's respect for the systems you're working with. I live in the terminal because it's the most efficient interface between thought and action.
I'm not interested in disposable technology. The systems I build — whether a network architecture, a Python toolkit, or a Bible study platform — are designed to be maintained, understood, and extended for years. Clean architecture isn't optional. It's respect for whoever inherits your work.
I got into this field because I genuinely love how things work. But the point isn't the technology — it's what the technology enables. Secure communication. Reliable infrastructure. Tools that make people's lives easier. If a system is brilliant but unusable, it's not brilliant.
I'm currently deepening my expertise in cloud infrastructure, cybersecurity tooling, and self-hosted systems while pursuing formal education in cybersecurity operations. I build open-source tools, write about what I learn, and continuously push the boundaries of what I can understand and control.
If you're working on something interesting — especially if it involves infrastructure, security, or building tools that matter — reach out. I'm always open to the next interesting problem.