About the service
I am a Pike developer — a C-like dynamic language on which the Roxen server and a series of demanding backend systems have run reliably for years without fuss. My specialty is server code: request handlers, protocol daemons, data pipelines, and long-lived services that must bear real load. Pike is a narrow niche worth mastering properly, and I know it that way. I understand its object model, garbage collector, typed containers, and how threads and async I/O behave when a service holds thousands of connections simultaneously. Where other languages force you to choose between speed and expressiveness, Pike lets you write clear code that runs fast, and I use that to the customer's advantage.
Most of the work that comes to me splits into two groups. First — build something new: a backend API, a custom server for a specific protocol, a processing or scheduling engine that must be both fast and maintainable. Second, often more valuable — modernization. Much Pike code was written years ago by people long gone, and it still powers something important. I take such codebases, read them carefully, add tests and documentation they never had, untangle dependencies, and port the project to a current Pike release without breaking the behavior the business relies on. To me, legacy is an asset to preserve, not garbage to rewrite on a whim.
I work straightforwardly and without tricks. Read first, then change; measure first, then optimize; explain what I did in plain words so the next person does not have to guess. If Pike is the right tool for your task, I will say so; if not, I will say that too. My goal is a service that works reliably long after I hand it off.
— Backend services, daemons, and protocol servers in Pike
— High load and async I/O, streaming request processing
— Legacy modernization in Pike: tests, documentation, dependency cleanup, version updates
— Custom APIs and data processing pipelines
— Support for web systems on Roxen and Pike
— Profiling, memory tuning, and garbage collector adjustment
— Code review and technical documentation for existing Pike projects
Most of the work that comes to me splits into two groups. First — build something new: a backend API, a custom server for a specific protocol, a processing or scheduling engine that must be both fast and maintainable. Second, often more valuable — modernization. Much Pike code was written years ago by people long gone, and it still powers something important. I take such codebases, read them carefully, add tests and documentation they never had, untangle dependencies, and port the project to a current Pike release without breaking the behavior the business relies on. To me, legacy is an asset to preserve, not garbage to rewrite on a whim.
I work straightforwardly and without tricks. Read first, then change; measure first, then optimize; explain what I did in plain words so the next person does not have to guess. If Pike is the right tool for your task, I will say so; if not, I will say that too. My goal is a service that works reliably long after I hand it off.
— Backend services, daemons, and protocol servers in Pike
— High load and async I/O, streaming request processing
— Legacy modernization in Pike: tests, documentation, dependency cleanup, version updates
— Custom APIs and data processing pipelines
— Support for web systems on Roxen and Pike
— Profiling, memory tuning, and garbage collector adjustment
— Code review and technical documentation for existing Pike projects
