I improve the backend services and internal tools behind Elytra Anti-Cheat (EAC). My focus is on making those systems more dependable and easier for the team to work with.
From incoming data to useful tools.
Bring incoming game data into the backend.
Make that data usable by the services.
Give the team tools to look into issues.
Embark is part of NexonNexon Co., Ltd.
I collaborate on a limited basis with Vaiiya Corporate LimitedVaiiya (VCL)
01 — ABOUT ME
My background is in backend development and anti-cheat.
At Embark, I work on Elytra anti-cheat for Wardogs, which launches September 10.
These days, I focus on improving the services and internal tools that support the studio’s anti-cheat efforts. It’s work that happens behind the scenes, but it helps create the foundation for a fairer player experience.
I approach that work with an emphasis on dependable systems and useful tooling: making services easier to operate, behavior easier to understand, and everyday engineering workflows more effective.
02 — MY WORK
I work on the services behind the studio’s anti-cheat. That means looking at how they behave, where they can be improved, and how to make changes without creating unnecessary complexity.
I care about code that other engineers can follow and services the team can depend on.
I work on internal tools that help the team use and manage those services. I want those tools to make everyday work easier, whether someone is looking into an issue or working through a routine task.
That starts with understanding how people use a tool and what gets in their way.
When something goes wrong, the team needs to understand what happened. I keep that in mind when improving a service, from how it handles errors to the information it makes available.
The goal is to spend less time guessing and more time working on the actual problem.
03 — HOW I WORK
I like understanding how things work and finding ways to improve them. These are a few things I keep in mind along the way.
“Innovate. Embrace new technology. Stay curious.”
Before changing something, I want to know why it works the way it does and what needs to improve. Taking the time to ask questions helps me avoid fixing the wrong thing.
Someone else will need to read the code or use the tool. I try to make that easier by keeping things straightforward and making decisions that are easy to explain.
Getting a change out is part of the work. I also think about how we’ll know it’s working, what could go wrong, and how the team will handle it.
CONTACT
Looking to hire an experienced Backend developer? Feel free to send me an email.