About
Software, data, and the teams that run them
I'm Viltho: a full-stack developer, data scientist and engineering manager with experience in operations management, the owner of nompany.com, and a gamer.
Most problems I work on don’t sit neatly inside one discipline. A slow process is often a data problem, a data problem is often a missing tool, and a missing tool is often a team that hasn’t had the time or the mandate to build it. Working across all three lets me follow a problem to wherever it actually lives.
Full-stack development
I build web applications end to end: data models, APIs and the interfaces on top of them. My current stack is TypeScript, React and Next.js on the front, with Python for data work and automation. I favour small, well-tested units over clever abstractions, and I treat performance and accessibility as part of the job rather than a later phase.
Data science
I use data to answer practical questions. That usually starts with the unglamorous part: getting data out of the systems or documents it lives in, cleaning it, and writing tests so it stays correct as sources change. From there it’s analysis, modelling or simulation, whichever gives the clearest answer to the question being asked.
Engineering management and operations
I lead engineering teams and have managed the operations around them. The work is about clarity: agreeing what matters most, making ownership obvious, designing processes that remove friction instead of adding it, and measuring outcomes rather than activity. Operations experience keeps me honest about what software has to do once it leaves the editor and meets real users, real volume and real deadlines.
Company
I own nompany.com.
Games
I’m a gamer too. Games are full of systems worth taking apart, and when a game makes me wonder how its numbers really work, I tend to build a tool to find out.
What’s on this site
The main project here is the Slayer Legends Analyzer, a free build planner for the mobile game Slayer Legends, with a set of guides that explain the game mechanics it models. It began as a way to answer my own questions about the game and grew into a small example of all three disciplines: a Python extraction pipeline with tests, a typed calculation library, and a web interface.
You can find my code on GitHub, or get in touch.