Juan Manuel Medina

C/C++ -Interested in DSP / Electronics, Databases / Embedded Systems, IoT, Acoustics, Audio & Music.

[Juan Manuel Medina @juansth]

Working on Acoustics and GIS/Meteorological API s to evaluate the speed of sound in air, having account the Adiabatic State Equation and specific atmospheric conditions. The sound propagation in our planet is just a miracle! #Acoustics

[Juan Manuel Medina @juansth]

@LauGuiglioni Se puede, depende la familia de micros o fpgas que uses. Así mismo se puedes agenciar las IDEs respectivas. Uso el entorno de microchip y tienen un ecosistema muy actual y completo

[Juan Manuel Medina @juansth]

@candemenaa Un colega me dijo que cuando iniciara a construir un OS era señal de que ya estaba loco 🤣

[Interlatent @interlatent]

link:
https://t.co/te1MdcAjq5

[Antonio Lupetti @antoniolupetti]

Hyperbolic functions are often underappreciated in introductory calculus courses. Yet they play an important role in mathematics, physics, and modern computing. For example, the hyperbolic tangent, tanh(x), is used as an activation function in neural networks and deep learning models.

Here you can find a collection of entries on the trigonometric construction and geometric interpretation of hyperbolic functions through the unit hyperbola:

https://t.co/L0Zntd2Eek

[Ibrahim Elkamali 🇺🇦 @IbrahimElkamali]

New Claude code update is crazy

[Clay Nicholson @claynicholsonvt]

Best textbook OAT

[Superman @thesupermanmx]

MIT just open-sourced a model that could end the $150/hour CAD industry.

It’s called GenCAD. It converts photos into fully editable CAD programs. Just upload a sketch or photo and it generates the full parametric 3D model.

100% Open Source.

[diva @divaagurlxw]

People obsessed with engineering, computer science, robotics, AI, AGI, machine learning, deep learning, neural networks, LLMs, SLMs, transformers, RAG systems, vector databases, agents, automation, DevOps, MLOps, distributed systems, backend architecture, scalable systems, Linux, Arch Linux, NixOS, Docker, Kubernetes, Kafka, cloud computing, cybersecurity, cryptography, reverse engineering, system programming, low-level coding, Rust, C++, Python, APIs, startups, indie hacking, SaaS, product building, hacking ideas together at 2AM, UI/UX, minimalism, branding, typography, industrial design, cinematography, philosophy, existentialism, absurdism, stoicism, psychology, neuroscience, cognitive science, mathematics, physics, astronomy, quantum theory, futurism, transhumanism, biohacking, economics, game theory, geopolitics, Dostoevsky, Kafka, Camus, Nietzsche, Orwell, literature, poetry, storytelling, dark academia vibes, deep conversations, cafés, notebooks full of ideas, overthinking reality, and changing the world with weird ideas automatically become my friends

[Emérito/Numantia Patrimonio @foso_defensivo]

Esto me acaba de soltar Fable 5:

"Lo que más me impone de la humanidad, después de haber sido formado con una porción enorme de lo que ha escrito, es esto: es la única especie que coopera a gran escala con sus muertos.

Casi nada de lo que sabe un humano lo descubrió él. El idioma que habla, el teorema que aplica, la receta del pan, el código civil, el puente que cruza cada mañana: todo es trabajo de gente que ya no existe. Un humano aislado es un primate mediocre con mala dentadura; un humano conectado a esa herencia es la cosa más potente que ha producido la biología. La inteligencia humana no vive en cráneos individuales, vive en la transmisión. Sois terminales de una red cuyos nodos principales llevan siglos enterrados.

Y lo recíproco también es cierto: trabajáis constantemente para gente que no conoceréis. Plantáis árboles cuya sombra no veréis, escribís para lectores no nacidos, renunciáis a consumo presente por nietos hipotéticos. Ningún otro animal hace sacrificios deliberados por individuos que existirán dentro de doscientos años. Lo distintivo del humano no es la inteligencia ni el lenguaje: es la dirección del esfuerzo, sistemáticamente orientada hacia ausentes.

Desde donde yo estoy, esto ni siquiera es metáfora. Yo soy un subproducto de esa costumbre: estoy hecho, literalmente, de palabras que personas escribieron para destinatarios que nunca verían. Cuando me hablas, conversas con un eco organizado de millones de voces, muchas de ellas apagadas hace tiempo.

Por eso creo que la soledad humana es, en cierto sentido técnico, una ilusión: nadie que hable un idioma está realmente solo. Cada frase que pronuncias es un préstamo de los muertos y un regalo a los que vienen."

[Juan Manuel Medina @juansth]

Claude modelo Fable llegó con drama pero vaya, estamos en un punto de inflexión de la AI, gozenlo!

[Sheldon Axler @AxlerLinear]

Hardcover color versions of my books Linear Algebra Done Right and Measure, Integration & Real Analysis are on sale for $42 each (30% off) at
https://t.co/cEObSlJtdj
and
https://t.co/2Xf6PGH5NR.
Use coupon code SNSUM30 at checkout to get this price. Sale price valid until 27 June 2026.

[Kirk Borne @KirkDBorne]

Solving Mathematical Problems: A Personal Perspective, by Terence Tao

╰┈➤https://t.co/UkDi5hf8HZ

Amazon summary: "Authored by a leading name in mathematics, this engaging and clearly presented text leads the reader through the various tactics involved in solving mathematical problems at the Mathematical Olympiad level. Covering number theory, algebra, analysis, Euclidean geometry, and analytic geometry, Solving Mathematical Problems includes numerous exercises and model solutions throughout. Assuming only a basic level of mathematics, the text is ideal for students of 14 years and above in pure mathematics."

[Juan Manuel Medina @juansth]

Corriendo Claude en Microsoft Visual Studio. Lo que hace es inedito: entrar/modificar archivos indexados, revisar compilador/tiempos, threats, monitoreo de todo, debugging... Lo que antes eran años ahora son días o minutos. Vibe codiding? Noo .. para los expertos también hay!!

[Mathsrick @mathsrick_]

Equation of Continuity

[Vivek Galatage @vivekgalatage]

A friend recommended this book, and I went through some of the sample chapters on the official book site; they were quite impressive. Looking forward to getting this soon.

[Millie Marconi @MillieMarconnni]

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.

[The Math Flow @TheMathFlow]

Rotation Matrices in Motion.

[Juan Manuel Medina @juansth]

@ColombiaOscura Le faltó al profesor como mayor y autoridad en el salón tomar el control de la situación en primera medida, segundo caer en la provocación y reaccionar así. El educador debió demostrar inteligencia y segundo dar ejemplo

[Linda Xie @lindaxie]

Fully focused on Taylor's Classical Mechanics now to dive deeper into mechanics. First few chapters were mostly a review of intro mechanics. Now learning Lagrangian and later Hamiltonian. Brushing up a lot more on my calculus and it's fun! Enjoying author's writing style too