
I'm speaking at @sfrubyconf! Buy a ticket and come say hi!

Principal software engineer @Wealthbox. Husband/Father. Health, travel, and tech enthusiast. Tech blog at jpcamara.com. Jokes at @logicalcomic.

I'm speaking at @sfrubyconf! Buy a ticket and come say hi!

Chat with Work is out: AI bots that work for you, in Europe, across 1,898 integrations. Write one sentence and you have a bot. It runs by itself and asks before it changes anything, unless you let it run.

Why start a new company on Rails, and AI, today - the opening keynote at @sfrubyconf. The deck is published: evilmartians.com/events/irin… Inside: - @garrytan “Ruby’s best years might be ahead of us” - why founders choose Rails for new products today: they want to worry about their product, not about plumbing. Conventions are gold. - what they said was missing over last 3 tears and what the community has built: everything! - why Rails is the best agentic framework for Humans! - engineering roles change into: product engineer, high-risk engineer and AI platform engineer and what each means - value of continuity and community in times of rapid disruption

Had such a wonderful time at @sfrubyconf. The ruby community is second to none, and folks like @palkan_tula @marcoroth_ and @paolino (and many many others) are helping push it forward daily. Thanks @inazarova for organizing such a great event!

We’re so sad the conference is actually coming to an end. Thank you so much for giving us the best time, see you next year!

Why let Claude have all the fun? I demoed my new library yrby-agent at @sfrubyconf, which lets an AI agent connect as a peer to your document, using @paolino’s RubyLLM behind the scenes
Starting to roll out today: Claude Whiteboards, Claude Sheets and Claude Data. Think a plan through on a board, build a tracker in a sheet, and tell a story with your data.

RubyLLM 2.2 is out! Released it on stage at @sfrubyconf Coding sandboxes with my new mxc gem. Skills support with my new skill gem. In memory, disk, and Active Storage file stores. Tools can ask a person and wait. Chats survive a deploy. Tests without a provider, 23 providers. All optimized for coding agents. The release I'm proudest of. paolino.me/rubyllm-2-2/

Love the story of Solid Queue from @rosapolis so much, and how commmunity collaborated on it, with @paolino and @jpcamara in the room!
Luckily, Rosa Gutiérrez (@rosapolis) didn’t lose her voice this time. She is on stage sharing the story of how Solid Queue went from 1.0 to all versions before 2.0, which will come out soon with sharding (after it’s tested in production).

We had an amazing time yesterday, see you again in a few hours. Thank you for sharing this week with us! 🫶🏻

"I think Ruby's best years might be ahead of it." Garry Tan (@garrytan) of @ycombinator opened SF Ruby Conference with words of appreciation for the community and @evilmartians. To Garry, agents need readable, consistent code that does things the same way every time, and that's what makes Rails conventions perfect for agentic coding. Watch the full opening:





I can't wait for everyone to vibe their own TLS impl. And their own OS, programming language, runtime! Definitely no bugs gonna happen. Make no mistakes. Dependencies are so over!
What’s going to happen to open source? A prediction: Dependencies are over. The same Brotli vulnerability impacted .NET, Node, Bun, Envoy and more. Dependencies are too big of a target. When rewriting a dependency is one prompt away, why take the risk?

People gotta realize that the whole idea of vulnerabilities being found and exposed in open source is what protects the industry from bad actors. Otherwise, they'll find ways into your app without you knowing (as they do). CVEs are a solution, not a problem. Update your dependencies!
What’s going to happen to open source? A prediction: Dependencies are over. The same Brotli vulnerability impacted .NET, Node, Bun, Envoy and more. Dependencies are too big of a target. When rewriting a dependency is one prompt away, why take the risk?