The Implementer
Systems, software, support, and communities. Doing this since the 90s.
I build, run, support, and grow the full stack. Systems and software. Support operations and communities. End-to-end ownership from planning through launch, reliability, and long-term care.
Jason, also known as Opie.
Ex-Twitch. Ex-Blizzard. Face of the Twitch global emote “OpieOP”.
Identity
Systems built with human care.
Focused on the hard work that keeps things steady. Clear support, calm operations, communities built on respect.
About
Rooted in the early internet.
I grew up in early online spaces where you learned by doing. Building tools, resolving conflicts, and keeping services running were all part of the same work. There was no line between the technical side and the people side.
That mix stuck. I care about how systems feel to the people who depend on them. I stay hands-on, choosing solutions that are dependable, understandable, and built for the long haul.
The early internet taught me that trust is earned through consistency. Details matter because real people depend on them. Every choice you make as a builder either adds friction or removes it.
I have always preferred removing it.
Why “The Implementer”
In MUD culture, the implementor held responsibility for the world and everyone in it. Not just the code, but the experience. The safety. The community. I keep the word "implementer" to reflect that same idea of stewardship, not status.
I own both spellings, implementer and implementor, as an origin story. Not a flex. It is a reminder that if I build something, I am responsible for it and for the people it serves.
What I Do
End-to-end ownership.
Connecting systems, software, and support into one steady practice, grounded in reliability and community care.
Systems and infrastructure
Long-term stability through thoughtful architecture, careful change management, and services that are straightforward to support.
Software
Clear, maintainable products that respect the people who use them and evolve without breaking trust.
Support and operations
Reliable support loops, incident response, and operational habits that keep teams calm and informed.
Communities
Programs, moderation, and culture work that make people feel heard, safe, and valued.
Partnerships and affiliates
Sustainable partner programs built on clarity, fairness, and mutual responsibility.
The Work
Principles, not logos.
I do not keep a logo wall here. The full timeline lives on my CV and LinkedIn.
- Simple systems beat clever systems.
- Close the loop with users and teammates.
- Communicate early, even when the news is not perfect.
- Document what matters and keep it current.
- Automate repeat work to protect focus.
- Respect users through clarity and care.
- Stability first, then new features.
Vineyard
Free hosting since 1998.
Vineyard is free hosting for MUDs, talkers, websites, and other online services. I started it in 1998 under the name Funcity because hosting fees were a barrier for new creators. It began on a repurposed computer in my room and grew from there.
Today Vineyard serves hundreds of users across a network of Linux servers in multiple data centers. I personally manage the infrastructure, the support, and the community around it. It runs on donations and Patreon support, but hosting is always free.
Vineyard is where my values show up most clearly. Lower the barrier. Keep things running. Be present. When someone needs help at two in the morning, respond. That kind of reliability builds trust, and trust is what holds a community together.
Support is not an afterthought. It is the daily work that shapes culture and keeps people coming back. How you show up when things break says more than any feature list.
Writing
Notes on the craft.
I write about stewardship, support culture, and the history of the communities that shaped how the internet works.
Contact
Get in touch.
Email is the best way to reach me. If it helps, put "support", "partners", or "affiliates" in the subject line.
contact@implementer.dev