About the service
I write and maintain code in Boo — a statically typed language in the spirit of Python that compiles directly to the dotnet/Mono runtime. Most often Boo is encountered in old Unity projects, and that is where I spend much of my work. If you have accumulated a heap of legacy Boo scripts that stopped building after an engine update, I will bring them back to life: make them compile again, move the riskiest parts to modern alternatives or wrap them so your current dotnet code can continue calling them without a complete rewrite. Since Boo preserves Python's clean indentation-based syntax while remaining fully statically typed, I easily move logic between it and C# without losing control over types. My tasks usually fall into several directions. First — rescue operations: I read through undocumented Boo modules, figure out what they actually do, and deliver a tested, buildable version. Second — dotnet integration: expose Boo assemblies to C# and vice versa, work through assembly references and ensure Mono and dotnet consistently understand types. Third — DSL design: Boo's open compiler pipeline and macro system make it an excellent foundation for small internal languages, and I have built DSLs for configurations and rules that even non-programmers can safely edit. Each order comes with readable source, comments, a short build instruction and unit tests where possible. I explain trade-offs upfront in plain language so you understand the reason for every change. Tell me what your Boo code should do, and I will honestly assess effort and risks.
