Periodistas con el objetivo de rescatar la Memoria y Patrimonio Audio Visual del Gremio. Sumemos esfuerzos en co-aprendizaje y colaboración.
Esperamos tu twitt
8/ Stop Scrolling 60 Minutes Before Bed
Blue light suppresses melatonin.
But worse — doom-scrolling keeps cortisol elevated through the night.
Replace it with a book, a stretch, or your partner. Your brain heals while you sleep — let it.
A Stanford professor just gave a public lecture on exactly how GPT, Claude, and LLaMA are built under the hood
no insider access required
just the clearest breakdown of modern LLM architecture I've seen
this lecture reveals the framework professors are paid up to $750K a year to teach
the gap between "I use ChatGPT" and "I understand how it works" is smaller than most people think
the most complete public breakdown of modern LLM architecture I've seen this year
Study calculus.
not because exams exist.
because reality moves.
• derivatives → how things change
• integrals → how change accumulates
• limits → what happens at the edge
• gradients → where systems want to go
• differential equations → how nature evolves
motion, heat, fluids, control, optimization, robotics, ML.
all of it speaks calculus.
without it, you see outputs.
with it, you see dynamics.
A 25-year-old housewife in Chennai earns ₹250/hour ($3) just by doing her normal housework.
She wears a phone on her head and records herself making coffee, cutting fruit, folding laundry.
These first-person videos get sent to AI companies training humanoid robots to handle real-world tasks. She shoots 90+ clips a day.
Her quote: "Who else will pay you ₹250/hour ($3) an hour just for doing housework?"
She's part of a growing gig economy in India where thousands are doing the same thing, filming everyday life to train the robots of tomorrow.
El Gobierno acaba de consagrar el triunfo de la "transparencia de papel". Un oficio de la Segpres justifica que la reunión entre el Presidente y el magnate de inteligencia de datos, Peter Thiel (Palantir), no se registre por Ley de Lobby. Las excusas son impresentables. 🧵
A French engineer who lives quietly in Paris has spent 30 years writing software that the entire internet now runs on without knowing his name.
He wrote the code that streams every YouTube video, every Netflix show, every TikTok clip. He wrote the code that runs the virtual servers underneath AWS, Google Cloud, and Microsoft Azure. He calculated more digits of pi than anyone in history. He has no Twitter. He has no marketing. He just keeps shipping.
His name is Fabrice Bellard.
Here is the story, because almost nobody outside the systems programming world knows what one man has built.
Fabrice was born in 1972 in Grenoble, France. He studied at École Polytechnique, the top French engineering school. He never went to Silicon Valley. He never built a startup empire. He just wrote code.
In 2000 he started a project called FFmpeg, an open-source multimedia framework for encoding, decoding, and streaming video. He was 28. The project did one thing nobody else had done well. It handled every video and audio format that existed, in one library, on every operating system. He led it himself for years.
Today FFmpeg is the invisible engine of the internet. YouTube uses it. Netflix uses it. VLC uses it. Chrome and Firefox use parts of it. Every Android phone, every iPhone, every smart TV, every video editing tool you have ever touched runs FFmpeg somewhere underneath. If you have watched a video on a screen in the last 20 years, Fabrice's code processed it.
He was not done.
In 2003 he started QEMU, a machine emulator and virtualizer. He wrote it solo until version 0.7.1 in 2005. QEMU lets you run any operating system on any other operating system. It became the foundation of modern virtualization. KVM, the Linux kernel hypervisor, runs on top of QEMU. Every major cloud provider, AWS, Google Cloud, Microsoft Azure, IBM Cloud, runs virtual machines on infrastructure built around it. The Quick Emulator is the most cited piece of cloud infrastructure code on Earth.
He kept going.
In 2001 he won the International Obfuscated C Code Contest with a small C compiler that grew into TCC, the Tiny C Compiler. TCC can compile and boot a Linux kernel from source in under 15 seconds. In 2004 he calculated the most digits of pi ever computed at the time, using a personal desktop computer and an algorithm he derived himself called Bellard's formula. In 2011 he wrote a complete PC emulator in pure JavaScript that runs Linux in your browser, a project called JSLinux that engineers still cannot believe is real.
In 2019 he released QuickJS, a small but complete JavaScript engine that fits where V8 cannot. In 2021 he released NNCP, a neural network based lossless data compressor that immediately took the lead on the Large Text Compression Benchmark.
Then he turned his attention to large language models. He built TextSynth Server, a web server with a REST API for running LLMs locally. He released ts_zip and ts_sms, compression utilities that use language models to compress text and short messages at ratios traditional algorithms cannot reach. He released TSAC, a very low bitrate audio compression system. In December 2025 he released Micro QuickJS, a new JavaScript engine for microcontrollers, separate from QuickJS, designed for environments with almost no memory.
Fabrice co-founded a telecom company called Amarisoft in 2012, where he serves as CTO. Amarisoft builds 4G and 5G base station software used by carriers and labs around the world. He has been running it for over a decade while continuing to ship personal projects from his own home page at bellard dot org
He has no Twitter. He has no Instagram. He gives almost no interviews. His personal website is a flat list of projects with no styling, no fonts, no marketing copy. Just titles and links.
A quiet French engineer who never moved to Silicon Valley wrote the code that quietly runs the internet.
He is still shipping.
10 RESEARCH WEBSITES THAT PHDS DO NOT WANT YOU TO FIND.
Bookmark this. Academia is gatekept by paywalls and you should not be paying.
1. https://t.co/X3NB1B5G0J
The largest open library on earth. Almost any textbook your professor assigned is here for free.
2. https://t.co/6PrA4Hu4py
The search engine for academic papers. Sort by citations to find the most influential research.
3. https://t.co/Dkd9aUkaPM
AI powered paper search built by the Allen Institute. Highlights every citation in context.
4. https://t.co/eDeHsCfyHJ
Plug in one paper, see every related study mapped as a graph. Reveals what experts actually read together.
5. https://t.co/5qJJorB7ny
An AI research assistant. Ask any question and get a structured table of papers with key findings.
6. https://t.co/XnSZ9WPRR1
Aggregates the conclusions of thousands of papers into one answer. Stops cherry picking.
7. https://t.co/wyQIVMApM3
The Spotify of papers. Recommends new research based on what you have already read.
8. https://t.co/LkdILeVnhD
Visualizes citation chains. Shows how an idea spread across decades of research.
9. https://t.co/1bu5BC44jU
Tells you which papers support, contradict, or mention any claim. Saves hours of fact checking.
10. https://t.co/7krhcpFEED
200 million open access papers in one searchable index. The world's largest free academic archive.
Most students pay $40,000 to access what these sites already make free.
el ingeniero que construyó Claude Code acaba de publicar un video de 28 minutos sobre cómo escribir prompts que realmente funcionan
he visto cursos de 300$ que no cubren lo que él muestra en los primeros 10 minutos
archivos CLAUDE.md, atajos de memoria, sesiones paralelas, patrones de prompting
todo en un video y completamente gratis
funciona seas desarrollador, principiante o alguien que lleva meses usando Claude
A journalist in 1987 rewrote the 2,500-year-old Tao Te Ching as a series of short parables about programmers, and the book became required reading inside Silicon Valley because every line of the joke turned out to be deadly serious.
His name was Geoffrey James.
He was not a famous engineer. He was a technology journalist who had spent years inside the offices of early software companies watching the same disasters play out over and over again.
Managers piling more programmers onto failing projects. Codebases collapsing under their own weight. Corporate hierarchies producing endless documents that nobody read. Geniuses being interrupted by meetings until they quit and went home.
He could have written a serious management book. Plenty of serious management books already existed and almost nobody in software was reading them. He decided to do something stranger.
He picked up a copy of the Tao Te Ching, the foundational text of Taoist philosophy written in China around 500 BC, and he rewrote it line by line as if Lao Tzu had been a master programmer.
The result was published in 1987 as The Tao of Programming. 151 pages. Nine books. Roughly 50 short parables. A comedy book on the surface and a philosophy book underneath, written in deliberately ornate language that made you smile while you were absorbing arguments that have aged better than almost anything else published about software in the last 40 years.
The opening line of the book is the giveaway. Thus spake the master programmer. When you have learned to snatch the error code from the trap frame, it will be time for you to leave. The joke is that he is parodying the kung fu master from the old Kung Fu TV show. The argument underneath the joke is that real mastery in software is not measured by what you can build. It is measured by how cleanly you can recover when the system fails.
The book has been passed around hacker communities continuously since the late 1980s. It sits alongside Fred Brooks's Mythical Man-Month on the required reading list of serious software teams. People who have never heard of Geoffrey James still quote his lines without knowing where they came from. The reason it has refused to die for 40 years is that every line of the parody was always disguising a piece of real wisdom that nobody else was willing to say plainly.
Here are some of the lines, and what each one is actually saying.
"Even a perfect program still has bugs."
The line is funny because it sounds like a contradiction. The truth underneath is that there is no such thing as a finished program. Every system you ship is alive. It is going to encounter inputs you did not anticipate, hardware you did not test on, and edge cases your imagination could not produce.
Treating any piece of software as finished is the single most common reason production systems fail. The masters in the book are calm about bugs because they have stopped pretending bugs are exceptions. Bugs are the default state. The programmer's job is to keep them from compounding.
"Let the programmers be many and the managers few. Then all will be productive."
The line is funny because every software company in the world does the opposite. The truth underneath is that programming is a kind of work that runs almost entirely on uninterrupted thought, and the more layers of management you stack on top of it, the more interruptions you create, the more meetings the programmers have to attend, the fewer actual hours of deep work get done.
Every manager you add to a software team subtracts more productive hours from the engineers than the manager could possibly add through coordination. Brooks proved this formally in 1975. James said it in nine words in 1987.
"After three days without programming, life becomes meaningless."
The line is funny because it sounds like an addict talking. The truth underneath is that genuine craft work produces a kind of meaning that almost nothing else in modern life provides. The programmer who has not touched real code in three days is not just bored.
They are emotionally underfed. The masters in the book understand that the work itself is not a means to a paycheck. The work is the reward. The paycheck is a side effect. Everything that interferes with the actual work, no matter how prestigious or well-paid it looks, is making the programmer's life worse, not better.
"A manager went to the master programmer and showed him the requirements document for a new application. The manager asked the master, how long will it take to design this system if I assign five programmers to it? The master replied, it will take one year. The manager said, but we need this system immediately or even sooner. How long will it take if I assign ten programmers to it? The master programmer frowned. In that case it will take two years."
The line is the punchline of Brooks's Law disguised as a koan. Adding programmers to a late project makes it later, because every new person has to be brought up to speed by the existing team, which slows the existing team down, which extends the timeline. The book teaches this in 60 words. The same lesson takes most managers 20 years of failed projects to learn, if they ever learn it at all.
The deeper pattern is the one most readers miss the first time through.
James was not really writing about programming. He was using programming as a setting for a much older argument that Taoist philosophy has been making for 2,500 years.
The argument is that the world is governed by simple principles that get harder to see the more cleverness you stack on top of them. Force does not work. Pressure does not work. More resources do not work. The only thing that works is restraint, simplicity, and the patience to let the right shape emerge.
Lao Tzu was talking about how to govern a kingdom. James was talking about how to ship software. The wisdom is the same. The kingdom is the codebase. The emperor is the project manager. The advisors are the developers. And the entire collapse of every doomed software project in the last 40 years has had the same root cause that the collapse of every doomed dynasty has had for the previous 4,000.
People mistook complexity for competence.
The book has been sitting on the internet for free for almost 30 years. You can read all 151 pages in an afternoon. Most people who run it as a joke walk away quoting it for the rest of their careers.
What James understood in 1987 is even more true in 2026. AI can now generate millions of lines of code in seconds. The bottleneck has shifted entirely. The bottleneck is no longer typing speed. The bottleneck is judgment. The bottleneck is taste. The bottleneck is the ability to look at a generated codebase and feel, without quite knowing why, that something is wrong with it. That kind of feel is exactly what the book was teaching all along.
The Tao of Programming flows far away and returns on the wind of morning.
The masters in the book were never joking. The world just took 40 years to figure out they were not.
बिना बिजली और ईंधन के चलने वाला यह जुगाड़ू वाटर पंप वाकई लाजवाब है।
विज्ञान और इंसानी दिमाग जब मिलते हैं, तो ऐसे ही आविष्कार होते हैं। ग्रामीण इलाकों के लिए यह तकनीक एक वरदान साबित हो सकती है। 💯
4️⃣ La energía sigue a la intención
📖 Kavanah es la intención pura detrás de cada acción.
La abundancia no se mide solo por resultados… sino por alineación.
1. La tefilá (oración) debe hacerse con kavanah (intención).
2. Kavanah proviene de la raíz hebrea "kivun" (dirección).
3. La oración efectiva es la que siempre está direccionada a un fin altruista.
4. Oración con buena intención es lo que trae Bendición.
#CaféKabbalah ☕💙