←
Marc Nuri2,471 posts
Marc Nuri avatar

Marc Nuri

@MarcNuri

Senior Principal Software Engineer at Red Hat. AI agents, open source, supply chain security. Created Kubernetes MCP Server; maintain @fabric8io and @jkubeio.

◷ Joined December 2008▧ 231 Photos and videos
Marc Nuri avatar
Marc Nuri@MarcNuri·11 May 2021

📌 I'm not an authority, I'm not an expert, anything you read here is just my (worthless) opinion. No soy una autoridad, no soy un experto, cualquier cosa que leas aquí es sólo mi opinión (sin valor).

FBI Dallas avatar
⟳ Marc Nuri retweeted
FBI Dallas@FBIDallas·Nov 17

The #FBI issued a FLASH advisory warning that cybercriminals and state-aligned hackers are exploiting ARTEX, a super intelligence-powered penetration testing framework, to automate attacks against businesses and organizations worldwide. ARTEX can accelerate intrusions from initial targeting to privileged access in under three hours. It was used in the October ConnectWise supply-chain compromise, which exposed Microsoft 365 customer environments and involved attempted authentication against more than 2,250 downstream tenants. The FBI is urging businesses and organizations to strengthen access controls, monitor suspicious automated activity, and report potential compromises to ic3.gov. Read more here: ic3.gov/CSA/2026/261113.pdf

Post attachment
Steve Yegge avatar
⟳ Marc Nuri retweeted
Steve Yegge@Steve_Yegge·Nov 14

I just finished talks about my software factories at two conferences. Afterwards a bunch of people came up and told me what they were surprised about. Here is a distillation of what people thought were hot takes from my two talks. First hot take: I tell everyone to slow down. Most speakers go on about how fast they're going, but I strongly believe in pacing AI outputs to human speeds. I regularly tell AI-pilled CIOs and CTOs to chill: almost nobody is _actually_ going fast with AI. Engineering still moves at engineering speeds, and business moves even slower. The ones pushing too hard are starting to see downtime for it. If you don't pace your AI to human speeds, everything starts breaking around you, even at small operations like my online video game. I only have about a dozen humans working with my factory, and only a few hundred active old-timer players in the community who get along well, and still, introducing AI has still been very rocky. My agents have, at times, overwhelmed my players with features, my accountant with emails, my merge queue with tickets, and my machines with load. Agents have pissed off my admins, resulting in name-calling, they've made messes in the game, and they've launched broken OSS without permission. The list goes on. I can get away with all this chaos because everyone involved in my operation is very forgiving. They're excited by the potential. But even so, I had to learn to slow down, real fast. And so that's what I preach. Hot take #2: Should you buy a software factory? Do you even need one? No. You probably don't need one. Factories take an extraordinary amount of upkeep. They turn into garbage mountains unless you put a frightening amount of time and tokens into curating them. I had to burn my previous five factories down since it eventually became cheaper to rewrite them than to fix them. So I'm not out there advocating for software factories or swarms just yet. If you do want one, be aware that it is a significant commitment of both money and human leadership to keep one running. Several people told me that I was the only one who stood up onstage, at either conference, and said Build, don't Buy. But my experience is that software factories grow to be highly bespoke to your domain. Mine is super tangled up with my game, and I think that's inevitable. Because the factory is not just building my product, it's supporting it too. It's a company in a box. And they're easy for Claude to build for you. Third and arguably hottest take: Next year will have a lot of human/agent and agent/agent office drama, resulting from bringing in AI employees, and it will be gloriously funny, but also frustrating. Many of you are already on this bandwagon, but everyone next year will have a personal chief-of-staff agent. Busy people, even hobbyists, will have whole entourages of helper agents. The hot take is that people will become so dependent on these little private entourages, that they'll bring them to work. Your people will talk to my people, etc. Whole protocols will emerge for private entourages negotiating work between humans, inside companies big and small. Nearly all humans will wind up having to start working with AI employees next year, and it'll be the beginning of the biggest cultural change we've seen in a hundred years. So that's the hot takes. Slow down. Only build a factory if you think you really need one. And focus on empowering yourself with your own agentic chief of staff (or team). Your entourage will define how you work with others, so start by perfecting how you work with them yourself.

Daniel Lemire avatar
⟳ Marc Nuri retweeted
Daniel Lemire@lemire·Nov 1

A CVE (Common Vulnerabilities and Exposures) is a publicly disclosed security flaw. They increased following a slight upward slope all the way to early 2024, when there was a sudden small increase... then starting in 2026, we went full exponential. In most instances, the vulnerabilities were pre-existing, so much of the increase is just our better ability to find the faults. This is of historical importance. We have never witnessed anything of the sort.

Post attachment
Jarred Sumner avatar
⟳ Marc Nuri retweeted
Jarred Sumner@jarredsumner·Oct 25

a growing part of how I feel about bun is this whole category of software - linters, formatters, package managers, type checkers, test runners, bundlers this used to be hard software to build and now it can be prompted into existence in a day or two

Polymarket avatar
⟳ Marc Nuri retweeted
Polymarket@Polymarket·Oct 23

BREAKING: China orders government agencies to develop plans to combat mass job displacement from AI.

⁵⁄₉ avatar
⟳ Marc Nuri retweeted
⁵⁄₉@fiveoutofnine·Oct 21

So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.

Claude avatar
⟳ Marc Nuri retweeted
Claude@claudeai·Sep 28

Introducing Claude Sonnet 5.5, the second model in the Claude 5.5 family. It’s a clear upgrade over Sonnet 5, runs more than 30% faster, and costs up to 30% less for most work.

0:13
Scott avatar
⟳ Marc Nuri retweeted
Scott@scottstts·Sep 25

My god this is such a good speech that every SWE needs to hear. You know what? Every person should hear it Keep the happy memories, eyes on the reality, be excited about the future. That’s the best that anyone can do

2:49
geoff avatar
⟳ Marc Nuri retweeted
geoff@GeoffreyHuntley·Sep 27

software is far from solved. a glimmer of ponderoos as to what 2026-2027 is as follows: we need better tools, compiler engineers are about to enter into a renaissance era when inferencing capacity is no longer the bottle neck, it becomes the compiler and verification tool chain problem. you want a decent amount of back prsssure on per unit of change but if that backpressure is too slow it punishes LLM mistakes thus reduces the amount of cycles per minute. what matters is being able to read a file, build an application and run tests in >milliseconds< programming language authors that focus on this and utilise llms to accelerate them and their community with an intense focus on cycle times will get ahead as it’s a safe bet that inferencing speed won’t be a limiting factor in the very very near future. it’s verification and how fast you can verify and pump the result back into the inferencing window.

Boris Cherny avatar
⟳ Marc Nuri retweeted
Boris Cherny@bcherny·Sep 25

🫶 writing that book was rewarding, and one of the hardest years of my life. I spent every night after work and every weekend writing and editing, and back then had to quadruple check every single example and code snippet by hand. My ex and I almost broke up over it (then ended up breaking up anyway). In the end the book turned out decently, and I swore I wouldn’t write another. Curious if your experience writing was at all similar