Benito Serna

Husband, Father, Rails developer, trumpet player,

[Benito Serna @bhserna]

@garybernhardt I am currently on the side of minimal constrains, because it will make slope anyway.

I have also seen that trying to keep the structure of the code in a shape that you like (either manually or as a glorified editor) helps to reduce the slope on new requests

[Benito Serna @bhserna]

@paolino oh thank you, I didn't know about it

[Aaron Francis @aarondfrancis]

Instead of going back and forth with your agent saying "hmm little more, no a little less" just ask it to build you a control to tweak it yourself, then give it the params you like.

[Samuel Williams @ioquatix]

It’s happening - compiled Ruby https://t.co/XKpYZoPyIv #rubykaigi #rubykaigiA

[Lewis Buckley @lewispb]

“rails query” is a great way to have your LLM / Claude / agent of choice query your production database. Read-only with a hook for logging and auditing. Works well with “kamal app exec” and Console 1984. Skill and blog post coming soon!

https://t.co/9wAQSopy4P

[Benito Serna @bhserna]

@jorgemanru I like the idea, it makes the file clean... also is hard to keep those "only" in sync.

The only "downsides" that I can see are that the errors will be on the controller and the before actions will run.

... but I am not sure if those are really problems.

Thansks for the answer!

[Benito Serna @bhserna]

@jorgemanru a question if you have time...

I was studying the routes.rb in Fizzy, Writebook and Campfire, and I noticed that you normally don't use "only" or "except" in your resources... you let the 404 happen at the controller level.

Is there a reason behind it?

[Joe Masilotti @joemasilotti]

This is Beervana, an iOS app I built entirely with HTML and a YAML file. It's powered by Ruby Native and available in the App Store today.

I didn't write a single line of Swift. Or even open Xcode.

[Mitchell Hashimoto @mitchellh]

https://t.co/RZlp39Wkrf

[Samad @_samadahmed]

Just recently I came across a really cool blog post from Evil Martians about TutorialKit.rb.

I decided to experiment and used the learnings from it to create a set of interactive tutorials designed to help you learn the basics of RubyLLM in about a lunch hour.

I figured I would share it here!

Also - I am especially interested in feedback, whether that is on the tutorials themselves, the pacing, clarity, or anything that felt confusing or could be improved.

https://t.co/Jsjoj6cOco

[Eira @eiranoirx]

https://t.co/ZBc42uEwQM

[Benito Serna @bhserna]

https://t.co/ODykJMhqfb

This video from @KentBeck (from two years ago... maybe a lifetime in AI years 😅) can help with this idea.

[Benito Serna @bhserna]

Today, with AI assisted development, breaking your code changes (commits / pull request) in "behavior changes" or "structure changes" is even more helpful.

[Benito Serna @bhserna]

"Your understanding allows you to fix the recall problem of agentic search, leading to better clanker outputs that need less massaging. And if shit hits the fan, you are able to go in and fix it. "

[Mario Zechner @badlogicgames]

I'm usually not one to write thought pieces without much technical depth. But here we go.

Slow the fuck down.

https://t.co/dcOwPK357F

[Mario Alberto Chávez @mario_chavez]

Claude Code auto-memory is genuinely useful. I use it. Auto-dream — the new consolidation pass that runs between sessions — makes it better.

But I noticed something when I started relying on it more: everything it saves is project-scoped and AI-decided. The agent picks what matters. The knowledge lives in one project's memory folder. Nothing crosses over.

That's a different problem than what recuerd0 solves.

The knowledge I actually want to preserve and reuse isn't always project-specific. An auth pattern I refined across four apps. A SQLite FTS5 quirk I debugged once and don't want to rediscover. The API conventions my team agreed on six months ago. That's not session notes — it's institutional knowledge, and it belongs somewhere I control, organized the way my team thinks, available to any tool we use.

With the recuerd0 agent inside Claude, I can query that knowledge directly from the conversation — same as auto-memory, but from a curated base I built intentionally, not one assembled automatically in the background.
Both have a place. Auto-memory for session continuity. recuerd0 for the knowledge worth keeping on purpose.

Self-host free or use the hosted version at $15/month for up to 10 users.

https://t.co/teXCY8gBmD

[Benito Serna @bhserna]

Is it possible to use vim mode in the new @cursor_ai glass?

[Kyle Aster @kneath]

I think at this point, every coder gets it.

We are going to see Bosses use this new technology to wreak havoc on the knowledge work economy. Some of it will be warranted. A lot of it won’t.

I wrote this to help my friends. What do you think?

https://t.co/gHEWvwO1Z0

[Benito Serna @bhserna]

I made a memory matching game to play with my kids.

Then I tried to make it a little better for others to play.

Maybe you can try it https://t.co/gM515xxrJg

[Mario Alberto Chávez @mario_chavez]

Hoy estoy lanzando @turestoapp, la aplicación de finanzas personales basada en el método japonés Kakeibo.

https://t.co/dZqpZziy1G

Tomas todos tus ingresos — sueldo, freelance, lo que sea — y los normalizas a una cantidad anual.

Luego registras todos tus gastos fijos: renta, Netflix, seguro, colegiatura, todo lo que ya está comprometido antes de que empiece el mes.

La diferencia dividida entre 365 es tu allowance diario.
Ese número responde la pregunta que reviso mentalmente antes de cualquier compra importante: ¿me alcanza?

No necesitas predecir cuánto vas a gastar en "restaurantes" este mes. No necesitas 20 categorías. No necesitas conectar ninguna cuenta bancaria.
Solo necesitas tu número.

Si hoy gastas menos que tu allowance, el día termina en verde. Si gastas más, sabes exactamente por qué — porque tú lo registraste.

El registro es manual y eso es intencional. Es parte del método Kakeibo: la consciencia del gasto proviene del acto de registrar, no del algoritmo que categoriza automáticamente lo que ya pasó.

Funciona con cualquier banco, fintech o fuente de ingreso. Porque no conecta con ninguno.

Prueba de 30 días sin tarjeta.

[Amelia Wattenberger 🪷 @Wattenberger]

https://t.co/KISd1HZWnB