Manuel Martín @ 🏠 @manolakis

⭐️⭐️ ¡¡𝗦𝗢𝗠𝗢𝗦 𝗕𝗜𝗖𝗔𝗠𝗣𝗘𝗢𝗡𝗘𝗦 𝗗𝗘𝗟 𝗠𝗨𝗡𝗗𝗢!! #VamosEspaña | #CopaMundialFIFA

😱 Este vídeo de Henry explicando el 0-2 de España es BRUTAL Luego en las televisiones de aquí tenemos a cuatro vendidos y a influencers que saben de fútbol lo justo o menos...

A 33-year-old woman at MIT wrote the code that ran inside the Apollo 11 lunar lander, and 20 seconds before Neil Armstrong touched the moon, her program made a decision the astronauts didn't know was happening that was the only reason the mission didn't crash. Her name was Margaret Hamilton. She led the team writing every line of code that would fly humans to the moon and back. The part almost nobody knows is that she had to fight to be allowed to do the work at all. Code in 1965 was not treated as real work. Rockets were serious. Circuits were serious. Writing code was something the men at NASA thought secretaries could do on the side. Hamilton was told this to her face more than once. So she started calling what her team did "software engineering." She used the phrase on purpose. In meetings. In memos. To force people to treat it as a discipline instead of a chore. Colleagues laughed at her the first few times she said it out loud. That phrase is now the name of the biggest engineering profession on earth. The story of what her code did on July 20, 1969 is the one every kid should be taught. Neil Armstrong and Buzz Aldrin were 3 minutes from touching down when the computer inside the lunar module started flashing an alarm. 1202. Then again. Then 1201. Five alarms in four minutes. The computer was telling the astronauts it could not finish everything it had been asked to do. The computer they were flying with had less memory than a modern microwave. Someone on the checklist had left a switch in the wrong position, and a radar the astronauts did not even need right then was flooding the computer with data. It was eating around 13% of the machine's brain at the exact moment every second mattered. In almost any other system, that overload would have frozen the machine. A frozen machine 30,000 feet above the moon means a crash. It means two dead astronauts and a third one orbiting alone above them, waiting for a signal that would never come. Hamilton's code did something else. She had built the software with a rule almost nobody in her field was using at the time. When the machine ran out of room, it would not treat every task as equally important. It would look at the list of jobs it had been asked to do, throw out the ones that could wait, and keep running only the ones keeping the crew alive. The radar was the low priority job. The landing was the highest. So the computer did what she had told it to do. It dumped the radar. It kept flying. The alarm was not a failure. It was the machine reporting that it was handling the overload exactly the way she had designed it to. Down in Houston, a 24-year-old engineer named Jack Garman recognized the alarm from a test his team had run months earlier. He shouted "Go" to the flight controller. The controller shouted it up to the crew. The landing kept going. Armstrong touched the surface with 25 seconds of fuel left. The part that gets lost in every retelling is why Hamilton had built that safety net in the first place. NASA had not asked for it. She had added it on her own, years earlier, because her 4-year-old daughter Lauren had once crashed the simulator by pressing a button during a test. The button was one the astronauts had been told they would never press. Hamilton wanted the code to survive that button press anyway. Her bosses told her it was a waste of time. Astronauts do not make mistakes. She insisted. The safety net went in. Two years later, on the way to the moon, an astronaut left a switch in the wrong position. The exact class of mistake she had been told would never happen. There is a photograph of her from that period. She is standing next to a stack of paper as tall as she is. Every page in that stack is the code her team wrote for the mission. She is smiling at the camera like she knows something the rest of the aerospace industry has not figured out yet. In 2016, Barack Obama put the Presidential Medal of Freedom around her neck and said the astronauts did not have much time, but thankfully, they had Margaret Hamilton. Every autopilot in every plane you have ever flown on uses a version of what she invented. Every pacemaker. Every self driving car. Every satellite in orbit. The idea that a machine should know which job matters most and drop the rest when it runs out of room is now the foundation of almost every safety system on the planet. She wrote it because a 4 year old crashed a simulator and nobody else thought it was worth fixing. The men in the room laughed at her for calling it engineering. Then her code was the only thing in the sky that did not fail.

Vibe coders’ daily struggles, summed up in 60 seconds 😁

Dennis Ritchie invented C in 1972, co-built Unix in 1969, and his code is running inside every device you are reading this on right now and the colleague who announced his death had to do it through a Google+ post because no journalist thought to check. He worked at Bell Labs in New Jersey for 44 years. He never gave a keynote. He never ran a company. He never appeared on a magazine cover. He just wrote code that became the invisible foundation everything else is built on. Here is what he actually built, and why it matters more than almost anything that happened in tech. In 1969, Bell Labs had just walked away from one of the most ambitious computing projects in history. The Multics project, a joint effort between MIT, Bell Labs, and General Electric, had collapsed under its own weight. Too complex. Too expensive. Too slow. Bell Labs pulled out. Ken Thompson and Dennis Ritchie refused to let the ideas die. Working in a small office in Murray Hill, New Jersey, Thompson wrote the first version of Unix in three weeks during the summer of 1969. One week for the file system. One week for the process management. One week for the command shell. Ritchie was working alongside him, and when the system needed a language that could express what they were building, he built one. In 1972 he completed C. C was not just another programming language. It was a different philosophy about what a programming language should be. Before C, most systems code was written in assembly, which meant every program was tied to the specific hardware it ran on. You could not move code between machines. You rewrote it from scratch every time. C changed that. It sat close enough to the hardware to be fast, but abstract enough to run on anything. When Thompson rewrote the Unix kernel in C in 1973, it became the first operating system that could be picked up and moved to a completely different machine without starting over. Portability was a new idea. Ritchie made it real. The branching that followed is almost impossible to overstate. Unix spread from Bell Labs to universities. At Berkeley, it became BSD. BSD became the foundation of macOS and iOS. Unix influenced Linus Torvalds, who built Linux in 1991. Linux now runs every Android phone, every major web server, every supercomputer on the Top500 list, and the overwhelming majority of cloud infrastructure at AWS, Google, and Microsoft. C became the parent language of C++, Java, JavaScript, Python, and Objective-C. Rob Pike, who worked across the hall from Ritchie at Bell Labs for 20 years, said it plainly: "The browsers are written in C. The Unix kernel that the entire internet runs on is written in C. Web servers are written in C, and if they're not, they're written in Java or C++, which are C derivatives, or Python or Ruby, which are implemented in C." Ritchie won the Turing Award in 1983. He won the National Medal of Technology in 1998, presented by President Clinton. He was head of System Software Research at Bell Labs for decades. He answered emails from strangers with technical questions until the end of his life. His home address stayed listed in the phone book. His colleague Brian Kernighan, who co-authored the definitive C textbook with him, said Ritchie was a private person who did no self-salesmanship. That was not false modesty. It was just who he was. He died on October 12, 2011, at his home in Berkeley Heights, New Jersey. He was 70. He had been ill for some time. The world did not notice until Rob Pike posted a quiet announcement on Google+, and the news spread through the programming community in hushed tones. No front pages. No tributes from heads of state. No candlelight vigils outside corporate campuses. The device you are reading this on runs code that traces directly back to what he built. So does the server that delivered it to you. So does the browser or app you opened to get here. Most people will never know his name. The ones who built everything you use every day do.

Happy 71st Birthday, Tim Berners-Lee, the inventor of the World Wide Web!

On 5 June 2002 Mozilla (also known as Mozilla .org ) released the Mozilla 1.0 web browser. The basis for Mozilla 1.0 was Gecko, an open-source rendering engine. #InternetHistory

Al conductor de autobús que se ha levantado en una parada y ha dicho "Los móviles con auriculares, por favor. Un respeto a los demás": Te deseo que nunca vuelvas a quemarte con una croqueta, siempre recuerdes tus contraseñas y encuentres aparcamiento a la primera.

Dennis Ritchie created C in the early 1970s without Google, Stack Overflow, GitHub, or any AI ( Claude, Cursor, Codex) assistant. - No VC funding. - No viral launch. - No TED talk. - Just two engineers at Bell Labs. A terminal. And a problem to solve. He built a language that fit in kilobytes. 50 years later, it runs everything. Linux kernel. Windows. macOS. Every iPhone. Every Android. NASA’s deep space probes. The International Space Station. > Python borrowed from it. > Java borrowed from it. > JavaScript borrowed from it. If you have ever written a single line of code in any language, you did it in Dennis Ritchie’s shadow. He died in 2011. The same week as Steve Jobs. Jobs got the front pages. Ritchie got silence. This Legend deserves to be celebrated.

After coding 100% agentic for 6 months, my key observation is that software design is more important than ever.

Programming used to put me into FLOW state often. That’s a big part of why I fell in love with it. Late night missions building games, apps, whatever, it felt great. Mihaly Csikszentmihalyi has a great quote on this: “The best moments in our lives… occur when a person’s body or mind is stretched to its limits in a voluntary effort to accomplish something difficult or worthwhile.” AI has kind of nuked the personal challenge part of that. I don’t fall into those same FLOW states nearly as often anymore. It’s a strange position to be in because I’m undeniably more productive, but some of the joy is gone. I still love building software, but now the enjoyment comes more from seeing products come to life and have real-world impact than from the actual process of writing the code. I’ll miss the deep flow states that came from fighting code for hours into the night, but I feel like I do need to find new areas that still offer that same sense of challenge.

What 10 Years in Spain Does To You 🍗

El Señor de los Anillos dirigida por George Lucas 😂

why does telling Claude your idea feel easier than telling actual people 💀 be honest… #Claude #DevMemes #ProgrammerHumor #AITools #AI

Una lección de periodismo. XD

Speaking of maps, "multiple import maps" are also coming in Firefox 151 nightly, so they could be baseline newly available soon

Now that Artemis II has launched we have 10 days to get everyone on Earth a Planet of the Apes costume so we can do something hilarious when the astronauts return 😁

Una genialidad en la TV británica, sobre cómo se toman sus vacaciones los ingleses en España

LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below