About the service
I write build automation on Starlark — a Python dialect that powers Bazel and Buck systems. If your builds are slow, unstable, or scattered across dozens of BUILD files as copy-paste, I transform them into small reusable rules and macros that are completely hermetic and reproducible.
What you get: custom rules with correct actions and output files; macros that remove boilerplate code from BUILD files; custom providers for passing structured data between rules; toolchains and platform configuration for cross-compilation; aspects for code generation, linting, and dependency graph analysis; repository rules that deterministically download and pin external dependencies.
Correctness matters to me. Every action explicitly declares inputs and outputs — nothing leaks from the host, remote cache and remote execution work immediately, and incremental builds stay fast. I write Starlark code idiomatically, with doc-strings and cover it with analysis tests so rules don't break silently on the next Bazel update.
Typical tasks: migrating a Make or CMake tree to Bazel, extracting a set of rules into a common library for multiple targets, adding language support (Go, Rust, Python, TypeScript, protobuf), setting up remote cache and CI, debugging non-deterministic outputs and cache misses. Send me your repo and describe the pain — I'll break down the work into clear verifiable steps with a fixed price and deadline.
What you get: custom rules with correct actions and output files; macros that remove boilerplate code from BUILD files; custom providers for passing structured data between rules; toolchains and platform configuration for cross-compilation; aspects for code generation, linting, and dependency graph analysis; repository rules that deterministically download and pin external dependencies.
Correctness matters to me. Every action explicitly declares inputs and outputs — nothing leaks from the host, remote cache and remote execution work immediately, and incremental builds stay fast. I write Starlark code idiomatically, with doc-strings and cover it with analysis tests so rules don't break silently on the next Bazel update.
Typical tasks: migrating a Make or CMake tree to Bazel, extracting a set of rules into a common library for multiple targets, adding language support (Go, Rust, Python, TypeScript, protobuf), setting up remote cache and CI, debugging non-deterministic outputs and cache misses. Send me your repo and describe the pain — I'll break down the work into clear verifiable steps with a fixed price and deadline.
