Martin Emde

@martinemde.com

Modularity @ Gusto, Rubyist

Just ran across this post by @andrewnez.bsky.social that puts words to my deep feeling of betrayal by Ruby Central in their awful governing of rubygems. "Package Registries Are Governance Providers," meaning their failure betrays the core promise of a package registry. nesbitt.io/2025/12/22/p...

Package Registries Are Governance Providers

Registries host files, but they also decide who owns names, how disputes resolve, and what gets removed. That second job is governance.

nesbitt.io

Skillet can now start up with an existing claude task list. $ skillet --task-list=mytasklist --prompt "Complete the assigned tasks" You can have another claude create and assign these tasks to a skillet worker (I think we could improve the interface though) github.com/martinemde/s...

GitHub - martinemde/skillet: 🍳 Run SKILLs & commands as Shell Scripts. Cook with Claude without the mess.

🍳 Run SKILLs & commands as Shell Scripts. Cook with Claude without the mess. - martinemde/skillet

github.com

And another thing! GitHub missed probably the one major thing we really needed them to do: separate AI actions from human actions. The "fine-grained" tokens are woefully inadequate for a situation where agents act on our behalf. GitHub ignored critical security controls to give us mediocre Copilot.

Joel Drapper 🇬🇧🇺🇦@joel.drapper.me · 7mo ago

It’s not just large code reviews that crash GitHub. I can’t even load the comment thread on this PR because it’s got 74 comments and GitHub probably has some N+1 query in there. 🤦‍♂️

Claude Code merged the duplicative slash commands into skills, and made skills better in the process. Happy to see this right as I was working on skills a bunch (the split was confusing, and a merger seemed inevitable). martinemde.com/blog/claude-...

Claude Code commands deprecated in favor of skills - Martin Emde

Anthropic pushed out a change to the docs that deprecates commands, pointing everyone te use the new improved skills with support for most of the same feature set.

martinemde.com

Lately it feels like the fan is just blasting at turbo speed and the ducts are full of shit but the fan is insane and the shit is hitting it all the time and the fan does not give a shit.

I’ve written countless throw-away headless claude scripts. - None work on the first try - Ugly prompts get buried in the ugly script - Permissions wrong, CLI flags wrong, nothing works - Output choices: Nothing / JSON flood. Agent Skills + Skillet fixes all of this: github.com/martinemde/s...

GitHub - martinemde/skillet: 🍳 Run Claude Skills as Shell Scripts.

🍳 Run Claude Skills as Shell Scripts. Contribute to martinemde/skillet development by creating an account on GitHub.

github.com

i think a core beef that i have with a lot of this "automation is bad" sentiment lately is that there is no inherent moral good in laboring the story of humanity is one of invention, where we improve our conditions by building things that help us do more things more easily

Post nicht verfügbar.

I made a claude code statusline that updates Ghostty's progress bar (that blue line at the top) as you fill up context. I know there's a lot of these out there, but this one uses starship directly for rendering, which was somewhat rare when I looked. github.com/martinemde/s...

GitHub - martinemde/starship-claude: ✳ claude code statusline rendered by starship

✳ claude code statusline rendered by starship. Contribute to martinemde/starship-claude development by creating an account on GitHub.

github.com

Interesting approach: Suppress Josef's comment, then suppress anyone else that isn't in support of the new "governance." Making a deal with the person that broke the last deal is futile, but what do you achieve by suppressing the people saying that? Suppression just brings more attention.

Martin Emde@martinemde.com · 7mo ago

Josef summed up problem of any new governance of rubygems in this comment: “The original governance was not the problem… The real failure was that one maintainer ignored it, and Ruby Core accepted that violation” github.com/ruby/rubygem...

You know… Ruby Central’s takeover of rubygems GitHub org ONLY worked because it could be executed within seconds, and by doing so, prevent the possibility of revert. If the ownership change was a PR it would never have been approved. If RC is “right”, why did they need the atomic switch?

@sethmlarson.dev and I went through months of intense, complex work to climb a steep and slippery learning curve, only to be stopped short at the very end by a hard ethical line we couldn't cross—it was gut-wrenching. I'm proud of what we did and I'm proud of what we didn't do.

Python Software Foundation@python.org · 9mo ago

TLDR; The PSF has made the decision to put our community and our shared diversity, equity, and inclusion values ahead of seeking $1.5M in new revenue. Please read and share. pyfound.blogspot.com/2025/10/NSF-... 🧵