@apri
iAccount based inUruguay
About this account
- Account based in
- Uruguay
- Connected via
- Uruguay App Store
Account-level information from X, not a live location or the device used for a specific post.
jPOS project founder. CX4CC. What one fool can do, another can. Naides es más que naides. https://nitter.cf/t.co/qLAgBkPShT
GF15xc
Joined May 2007
- Tweets12.8K
- Following255
- Followers1.6K
- Likes6.8K
Another week working on the #jPOS Control Plane. 1.1M LOC and counting.
Alejandro Revilla retweeted
Moderately convinced that the entire premise of today's Claude Code style "agentic memory" is flawed since it requires the agent to know today what will be important tomorrow. Search-oriented memory will be much more useful. Adding this to Mjolnir through our sessionwiki fork.
After 40+ years, I'm retiring my Clipper '85 personal ledger and replacing it with a new Markdown-based one. The main goal is to make it time-proof: a simple, human-readable format with no dependency on a particular application. As long as there's cat, the ledger will remain readable.
You can try it at github.com/ar/mdl
New #jPOS Client ISO 8583 Simulator.
ISO 20022 coming next.
jpos.org/blog/clientsim-cont…
People say @htmx_org sucks, problem is they are not using 3.0, the real deal.
#jPOS Vendor a dependency - then give it back
jpos.org/blog/vendor-a-depen…
Bilingual superpower: ZipTalk.
PonyTail reduces cognitive load. CaveMan compresses hard. Llanito-inspired code-switching picks the most direct word—English o español.
Zip a conversation: preserve meaning, process it más rápido. UnZip to polished prose. RepackTalk a thread.
More bandwidth between people. Joe 90 glasses—absorb more, no overload.
Link: github.com/ar/ziptalk
---
Original text:
I think I stumbled onto a superpower for bilingual (English/Spanish) speakers.
I call it RepackTalk.
It combines:
• PonyTail for reducing cognitive load.
• CaveMan for aggressive compression.
• Llanito-inspired code-switching (English/Spanish) for semantic compression.
The inspiration came from hearing how naturally bilingual speakers in Gibraltar switch languages, effortlessly choosing whichever word carries the idea more directly.
You can ZipTalk a conversation to preserve meaning while making it dramatically faster to process, then UnZip it into polished prose—or RepackTalk an entire thread into the best possible version.
For me, it feels like increasing the bandwidth between people.
Or maybe like finally getting the Joe 90 glasses—absorbing far more information without overwhelming your brain.
github.com/ar/ziptalk
Oh-my-bash, make yourself a favor. Change your PS1 to `\[\033[32m\]$(parse_git_branch)\[\033[00m\]\w$`. That's all you need. I've been using this for 20+ years.
JBang rocks. One of my first agent instruction is always “no Python scripts, use JBang instead”.
🎉 JBang just passed 3 MILLION binary downloads!
A 2019 experiment — "why should running a small Java program need a whole project?" quietly became Java infrastructure. ~1,000 downloads/day, 130+ countries, From Java 8 to 26+
Thank you 🙏
jbang.dev/learn/somehow-jban…
My AI-powered Dunning–Kruger graph (below) is meant as a joke—but only partly.
AI has made every developer feel a little smarter. The result is a new kind of contributor: the AI-poisoned developer, armed with confidence but short on understanding.
This 20-year-old post from the Google/Subversion team feels more relevant than ever:
jpos.org/blog/2007/04/how-op…
This is absolutely true. I think the number is closer to 20×. I also think body shops are in serious trouble. Fortunately for them, the market hasn't fully priced that in just yet.
I talk to engineers at other companies every day and hear the same thing: one person is 10x'ing their output with Claude but the rest of the org hasn't caught up.
Watching teams adopt AI, I keep seeing the same 4 steps.
I mapped them out here: Steps of AI Adoption claude.ai/code/artifact/bfdf…