About the service
I create compact backends and domain-specific languages (DSL) on PicoLisp — a minimalist practical Lisp that fits an entire application stack into a tiny volume. PicoLisp carries its own application server, a transactional object database, and Pilog — an embedded Prolog engine, so you get a fast backend without gluing together a dozen dependencies. Fewer moving parts, less server load, and code you can still read a year later.
What I do: REST and JSON endpoints, background handlers, data pipelines and rule engines expressed in pure DSL that reads like your domain, not boilerplate. I use Pilog for constraint logic, pattern matching and inference, where logical queries beat imperative loops, and the native object database — for storage without an external SQL server when appropriate for the scale.
Typical tasks: turn raw specifications into a small testable core; wrap legacy formats in readable mini-language; build a prototype in days, not weeks; replace an over-engineered service with a concise PicoLisp process. I write tests, document DSL grammar, and hand over production-ready code with clear run instructions.
Describe the goal — API, interpreter, scheduler, rule engine — and I'll honestly assess the scope, keep the solution minimal, and deliver a small product that does exactly what's needed.
What I do: REST and JSON endpoints, background handlers, data pipelines and rule engines expressed in pure DSL that reads like your domain, not boilerplate. I use Pilog for constraint logic, pattern matching and inference, where logical queries beat imperative loops, and the native object database — for storage without an external SQL server when appropriate for the scale.
Typical tasks: turn raw specifications into a small testable core; wrap legacy formats in readable mini-language; build a prototype in days, not weeks; replace an over-engineered service with a concise PicoLisp process. I write tests, document DSL grammar, and hand over production-ready code with clear run instructions.
Describe the goal — API, interpreter, scheduler, rule engine — and I'll honestly assess the scope, keep the solution minimal, and deliver a small product that does exactly what's needed.
