Hi, I’m Billy

I’m an independent engineer who fixes the sharp edges in the tools developers actually use.

🚀 Recent Impact

n8n Public API

I identified and documented a bug where the Public API stripped Code/Function node code and ignored in-place node updates, breaking CI-style workflow management.

• Issue: https://github.com/n8n-io/n8n/issues/18574
• Fix shipped in core as “Allow dynamic node parameters in Public API schema”
• Release: https://github.com/n8n-io/n8n/releases/tag/n8n%401.119.0

Google Gemini CLI

I opened a PR to sanitize tool function names so they comply with Gemini’s constraints, eliminating 400 INVALID_ARGUMENT errors for tools.

• PR: https://github.com/google-gemini/gemini-cli/pull/12941

🔧 What I Work On

I focus on AI/devtool infrastructure, especially:

• Workflow engines (like n8n)
• AI/Agents, , Orchestration, CLIs, MCPs, APIs, SDKs...
  ...and plenty more!

❤️ What Your Sponsorship Supports

Right now, when I debug and patch these issues, I pay for the infra and API usage myself. Sponsorship allows me to:

• Reproduce and fix deep, ecosystem-level bugs in AI/devtools
• Ship patches and examples that unblock thousands of developers
• Prioritize the open-source tools and integrations you care about

👇 Who Should Sponsor

You’ll get the most value if you are:

• An AI/devtools company (Replit, Anthropic, NVIDIA, Lovable, etc.)
• A team relying on n8n, Gemini CLI, or similar infra in production
• An org that wants the open-source ecosystem around your tools to be more reliable and better documented

🎁 What Sponsors Get

I keep it simple and honest:

• Public credit in relevant READMEs/issues/PRs (when appropriate)
• I bias my time toward:
  • Bugs and rough edges affecting your stack
  • Better docs, examples, workflows for your tools
  • Integrations/glue code your users are currently hacking together themselves

Higher-tier sponsors:
I’m happy to coordinate on a rough priority list of ecosystem issues you want improved (all work remains open-source).

🌍 Why This Matters

Modern systems quietly depend on a massive amount of open-source glue.
When that glue is brittle, everyone wastes time on the same debugging threads, workarounds, and vague 400 errors.

Sponsoring me helps:

• Turn real-world pain (like the issues above) into merged fixes and widely-used improvements
• Support an independent engineer focused specifically on AI/devtool reliability

If you or your org rely on these tools and want them to be better for everyone, your support goes directly into that work.

Thank you for even considering it.
— Billy / ProdByBuddha