About the service
I've worked with Ceylon — the statically typed language for the JVM originally created at Red Hat — for many years and can maintain it even after tool updates stopped. If you've inherited a Ceylon project and nobody on your team dares touch it, reach out to me. My work has three parts. First — maintenance: I fix bugs, patch modules, update dependencies, and make sure your JVM application keeps building and deploying on the runtime you already use. Second — understanding: I read the union and intersection types that make Ceylon so expressive, document how modules connect, and explain the system's behavior to your developers in plain terms. Third — migration: when you decide to leave the language, I plan and conduct a careful transition to Java or Kotlin, preserving the type guarantees your code relied on and mapping Ceylon's powerful type system to your new stack's idioms. I never rush rewriting. First I build a map of the module hierarchy, cover existing behavior with characterizing tests, and migrate code in pieces so the application stays working throughout. The result is a building build, a documented module map, a migration plan with risk assessment, and clean commits for review. I use Ceylon every week and treat its quirks as familiar territory. Describe your codebase size and target runtime — and I'll give you an honest estimate.
