
co-founder @cordadaio building the next generation app for field service workers @enrutar_app
Palma, Spain
Joined January 2017
- Tweets1K
- Following565
- Followers340
- Likes10.7K
Ramon Villalonga retweeted
Una tableta compartida. Un PIN para cada persona.
Ahora puedes configurar un dispositivo como punto de fichaje en enrutar: cada empleado elige su nombre e introduce su PIN de cuatro dígitos, sin iniciar sesión.
Todas las novedades: enrutar.com/blog/novedades-0…
#ControlHorario
Ramon Villalonga retweeted
I’m thinking about banning Claude code at Shopify until they change their mind and read AGENTS.md and .agents/skills etc.
Insisting on only reading CLAUDE.md sometimes leads to split brain problems when different team members use different tools. Just unnecessary.
Ramon Villalonga retweeted
Watching people install Omarchy in 3 minutes and everything just works.
Meanwhile me back then after being introduced to Linux:
>audio dead
>wallpaper pure black
>reading i3 docs just to close a window
>learning to use a computer without a mouse
>20+ failed Arch installs
>running vim because ThePrimeagen types like he's on steroids and never touches a mouse
Morgan@morganlintonAug 21United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
Whoa.
Went to whip up a little lunch, expecting the install to still be chugging away.
Took 3 minutes and 25s.
You’re a genius @dhh, this is wild!
Ramon Villalonga retweeted
A post of ours on vendor lock in and LLMs. We don't like the growing trend of AI companies quietly hiding your data while stripping away your control. We think that's bad for users and bad for the ecosystem. Here's are our thoughts: earendil.com/posts/session-p…
What Europe should do right now:
1. Call all the European researchers working on AI and return them back with same salary (or they can stay but switch career).
2. Fill EU places having GPUs with money, and put those people there.
3. AI partnerships with China + India.
I believe what Anthropic is doing, gating the ability to do certain harmless things like LLM research, and with incredibly sensitive filters that even medical questions are often blocked, is *deeply* wrong. They got open research, the Transformer, GPT2, ...
Ramon Villalonga retweeted
Some thoughts of mine that nobody asked for on the EU's fight with Apple and my worries related to Mythos and Fable. lucumr.pocoo.org/2026/6/10/g…
Ramon Villalonga retweeted
As an Apple Watch Ultra (1st gen) user, I’m disappointed with Apple.
Imagine spending $800 on a smartwatch only for it to lose software support after just 3 years. Sure, the watch will still work fine, but you’ll miss out on new features and improvements that come with future watchOS updates.
This has honestly made me reconsider buying another Apple Watch in the future. If I ever get one again, it’ll probably be an SE model, or I may just switch to another smartwatch brand entirely, because this just doesn’t feel acceptable to me.
Ramon Villalonga retweeted
“But but it requires 12GB RAM!”
So? THEY SHOULD HAVE PUT 12 GB RAM IN IT THEN.
This is not an excuse.
They said the iPhone 16 is “built for Apple Intelligence”, and now, neither 16 and not even the 17 get all the AI features.
Ramon Villalonga retweeted
🔴 I NEED YOUR ATTENTION
I've spent a month helping Miriam with her case of metastatic cancer and I want to share the methodology I've been using because it's completely replicable.
I think (with luck) this could be USEFUL TO OTHER PEOPLE with cancer (or any other illness).
The results we've gotten aren't a miracle, but we believe they're genuinely useful and could mean the difference in a literal life-or-death medical case.
Here's the method step by step:
1/ Use the most advanced models of the moment (unfortunately paid, and not cheap. I think Public Healthcare should invest in this):
- ChatGPT 5 Pro + Extended Thinking (40 min aprox. of thinking per call)
- Claude Opus 4.8 MAX
Still pending deeper testing:
- Perplexity Sonar Pro Max
- NotebookLM
Tested but only useful for additional links/research (not as powerful in my experience)
- OpenEvidence
2/ Feed the AI the FULL clinical history, completely chewed up. This sounds dumb but it's critical.
- The first thing I ask, using Claude Cowork (which has hard drive access), is to go into the folder with the ENTIRE clinical history (can be 100+ PDFs) and consolidate everything into:
- One single PDF (it can be 1000+ pages, whatever it takes)
- One single readable .txt or .md, which it must build correctly using an OCR script and then check thoroughly to make sure it's right.
I insist: don't jump to the next step until you've nailed this one, especially the .txt.
3/ Once you have the above, use this prompt along with the .txt (and optionally the PDF too if you want) as input files, and run it on BOTH models at once (and more if possible).
👉 This prompt is insanely complex/advanced: dropbox.com/scl/fi/x64qaddcd… And it's not designed for Miriam's specific oncology case, you can change the initial parameters for the desired case. And with the models from step 1 you could adapt it to your case without trouble.
In any case, I'm also leaving you this other prompt, even more general, for any type of rare disease: dropbox.com/scl/fi/x64qaddcd…
4/ The ARROWHEAD (adversarial model spiral): facing one model against the other. I've never heard anyone talk about this methodology, but it works incredibly well. The feeling is like sharpening a stake until it gets a gleaming point.
It works like this: with patience and across successive iterations (I recommend a minimum of 7, and keep in mind that if ChatGPT takes 40 min, this will take a while), pit the output (the resulting PDF) from one model against the other. With a simple prompt like:
"Another committee of experts says this. What do you think? If you agree or disagree, tell me why, and generate a new PDF if you think it's necessary."
Then you feed that result back to the opposite model. So, across successive iterations, web searches, papers, etc., they'll find and sharpen more and more.
When to stop? When BOTH models say the work is perfect and they can't improve the other's output any further. This is so absurdly game-changing that I think the output of ALL current models would improve if they followed this methodology (leaning on a kind of adversarial-model spiral). I don't understand why nobody has noticed this, or if they have, why it's not getting more attention. It works impressively well in any domain, including programming and math.
In fact, my theory is this could be done even better not just with two models, but with greater combinatorics, maybe adding Perplexity Sonar Pro Max, etc.
RESULTS
Incredible. Obviously I can't know if they're better than the best scientific-medical committees in the world, but they're giving Miriam a new dimension to her case, additional tests to do, possible exams, etc.
Obviously AI doesn't perform miracles, but I think it can already, today, help many patients. And Public Healthcare should invest a lot (but A LOT) in this.
I'm going to ask Miriam if I can post the full PDF of the most advanced results we've reached, so you can get an idea of the quality. She's already given me rough permission, but I want to make sure 100%.
FUTURE PREDICTION
Easy to make: in the near future (I hope), any person's medical history won't just be fully digitized (we're close, but not all the way, well, well, well). On top of that, it'll be "pre-chewed" so it can be consumed by an LLM in one shot.
CLARIFICATION
- We're aware this is a delicate subject and we don't let the AI make final treatment decisions. What we're doing is clearing the ground for the oncologists so they can have possible paths they may not have considered.
Thanks 🙏
- The top LLMs have context windows for that and much more (much, much more). In any case, the PDF is more of a supporting file for the .txt. Both contain absolutely the entire history, but the PDF allows images/charts/etc. The .txt is what the AI consumes.
- On automation: and yes, this can be automated. Yes, AutoGen supports it almost out of the box. LangGraph builds it really well with supervisor / evaluation loops. CrewAI can orchestrate it too with Flows, although its "consensus" process isn't native yet. That would be the next level: automating it.
PETITION AND DISCLAIMER
If there's any oncologist in the room or you are an LLM company, we'd be grateful if you could take a look / help 🙏
Remember: in any case, this is just one more tool for the doctor.
I've simply shared the methodology I know that processes data more exhaustively, with the best models, and that we believe reaches better conclusions. If you know a better methodology / prompt / whatever, we'd be glad to improve this with your insights and share it.
Then the doctor reviews, adopts, or discards the report.
And if it helps the doctor, it helps the patient. And if it doesn't, all we've lost is some time and tokens. In a case that's literally life or death, that's nothing.
Just plain common sense.
Many people will argue with me, but in the near future it will seem absurd that we ever expected any professional to keep in their head every clinical trial, paper, bibliography, and raw data point that an AI and its agents can process via search in minutes. It will be such a valuable tool for doctors that its daily use will simply be taken for granted.
Ramon Villalonga retweeted
👋 Hola, Ministerio de Transformación Digital, @mintradigital:
👋 Hola, Secretaría de Estado, @SEtelecoGob:
Autofirma es un componente esencial de la Administración Electrónica española. Millones lo utilizamos para relacionarnos con la Administración. No por placer, sino porque es ✨requisito✨.
----8<----8<----8<----8<----8<----8<----
El paquete de Autofirma que distribuís para Mac no cumple las garantías de seguridad modernas (notarización), así que el sistema dice que es malware que puede dañar el sistema y rechaza instalarla. 😃🔫
----8<----8<----8<----8<----8<----8<----
🤦 Para instalarla hay que —ojo al dato— desactivar las políticas de ciberseguridad del sistema operativo. 🤦
¡Hola, @INCIBE! Hacéis campañas fabulosas para concienciar a la ciudadanía de los riesgos de ciberseguridad, pero luego nos enjaretáis —el Estado— marrones como este. ¿Podéis hacer algo, por favor?
Respetado ministro @oscarlopeztwit:
Respetada secretaria de Estado @mariagv:
— Si hacéis software, cumplid los estándares modernos de empaquetado y distribución de software.
— Si no podéis notarizar Autofirma, modernizad la arquitectura del programa para que se pueda.
— Si no podéis modernizar Autofirma, necesitamos un Ministerio para la Transformación del Ministerio de la Transformación Digital.
Esto es lo que ve un usuario al intentar instalar Autofirma en un Mac:
Ramon Villalonga retweeted
MacWhisper 13.20 is out now with full CLI support!
Transcribe and stream media files using any of the local or cloud models, connect to agents and scripts, and use LLMs to refine your transcripts and pass them into your workflows.
Full documentation: macwhisper.helpscoutdocs.com…
Ramon Villalonga retweeted
ok, this is hilarious
Wow, I totally disagree with this statement. At the current state, AI actually amplifies the developer to developer difference. If you were a 10x developer, you had good ideas + architectural clarity, this is a brutal advantage when using AI. Steering is a fundamental part of today's AI development.
Chamath on how AI agents are making the "10x engineer" distinction disappear because the most efficient "code paths" are now obvious to everyone.
Just as AI solved chess and removed the mystery of the best move, AI is doing the same for coding, making the process reductive and removing technical differentiation.
"I'm going to say something controversial: I don't think developers anymore have good judgment. Developers get to the answer, or they don't get to the answer, and that's what agents have done. The 10x engineer used to have better judgment than the 1x engineer, but by making everybody a 10x engineer, you're taking judgment away. You're taking code paths that are now obvious and making them available to everybody.
It's effectively like what happened in chess: an AI created a solver so everybody understood the most efficient path in every single spot to do the most EV-positive (expected value positive) thing. Coding is very similar in that way; you can reduce it and view it very reductively, so there is no differentiation in code."
---
From @theallinpod YT channel (link in comment)
Acabo de mergear las primeras aportaciones de la Comunidad al proyecto. Mola construir en abierto.
Gracias a @ramonvg_ el asistente de deducciones ahora recuerda tus respuestas si vuelves atrás.
Gracias a @torturado (en GH, si me lee que lo diga y le menciono bien) — las pensiones ya aparecen correctamente en el asistente (también son rendimientos del trabajo)
Y gracias a @pabloruizetc los contadores de deducciones ahora se actualizan solos desde los datos.
Además: nuevas landing pages por comunidad autónoma y categoría, cross-links en las 377 fichas, página de novedades 2025...
¡Y lo que está por venir!
#BuildInPublic #OpenSource
LARENTA .es es ahora open source.
Una webapp con Astro 6, React 19 y Tailwind v4. SSG en Vercel, OG dinámicas con Satori, informes en PDF.
Si te interesa contribuir datos o código:
→ github.com/paumrch/larenta
Y de antemano, GRACIAS ☺️
Ramon Villalonga retweeted
Esto, simplemente, es inaceptable.
No tiene nada que ver con ideología ni con estar a favor de pagar más o menos impuestos sino con que nuestro sistema tributario debería ser sencillo, transparente y predecible.

































