How does this compete with built in secrets management already available in Coder, Claude, and Copilot?

Do I need another “C” in my workflow?

I'd say the two biggest things are Portability, and Ergonomics.

For portability your secrets in those platforms can't move around with you, but with Capy they can move with you wherever you're doing your work. Your local machine, your sandbox, etc.

Capy also helps you deploy your secrets into Coder, Claude, Copilot and whatever other Clever product you prefer to use ;)

For ergonomics, Capy is built from the ground up as a CLI, which means it's extremely flexible in where you want to use it. I'm also working currently on making it work SUPER well in agentic coding workflows. There's going to be more on that coming soon!

Feel free to join us in Discord to find out - https://discord.gg/yHMaXFpj

We are pretty open about what we are up to

Thanks for pointing this out. We are aware of this and as we move closer to version 1.0 we plan to address this and other issues.

Kind of an odd take. The first folks performing what we now call DevRel were engineers, founders, VPs, and directors. Even now a vast majority of DevRel practitioners are engineers. Which means they do more than one job.

As far as being disrespected or viewed as divas, it's ironically engineers that meme-ify DevRel folks.

As far as the three points, much like every engineer that writes a post about the pointlessness of code tests in the interview process, sometimes things don't change. Granted, those three points haven't been made in "every single devRel blogpost you read since 2012" since the term DevRel was really coined in 2014-ish. but that's not really the issue.

No, there are still many things unresolved in the DevRel industry. It's much bigger than it was, yet "pure engineers" slough it off as meme-worthy and management still can't see past it being marketing or pre-sales. So more people add their voice in an attempt to improve things.

You don't stop saying something needs to be fixed just because it's been said before. You keep saying it until it's fixed.

THIS. "You don't stop saying something needs to be fixed just because it's been said before. You keep saying it until it's fixed." 100%

Thanks - that sentence actually felt really good to write.

Full disclosure: I work at Humio. Great, cost-efficient monitoring, sub-second ingest latency, on-prem or in the cloud. Feel free to check it out - humio.com

Runs smoother than the ELK stack.

What golden blessing would that be?

The "Official Ruby on Rails Hosting Provider", that they had back in the day, before it went to Engine Yard.

I can vouch for it - it's solid. Feel free to jump into #engineyard on IRCFreenode if you have any questions - or just use the trial hours to spin up a staging version and give it a try.

Dude - I can't believe they held your family and wouldn't let you leave! I was shocked at the way they treated Zak and I when we left, but never expected anything of this magnitude.

At least you pulled off an amazing conf despite all the following bullshit.

yeah man - cannot risk any confrontation with family around! I heard about your checkout and their goof-up in billing. Jokers had the audacity of telling me that our attendees were rude and abusive!

Glad you had a great time. I wonder when I am going to say - "Hey we nailed it - the conference was successful without a hitch" ;)

Ditto that. The Organizers made this event amazing regardless of some of the logistical issues they were presented.

Location really has little to do with. While SF is a bit of a hipster enclave, so are a lot of places with plenty of tech companies.