Marc Nuri

📌 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).

I've already gone through this thought exercise. Why does it matter? "It shouldn't matter because the AI manages it." This logic is completely flawed. You have to see it in practice. AI does not turn an engineer into a 10x engineer. I can supe up a Civic and it will do 0-60 faster than a stock Porsche. Now take both of those cars to a track and see what happens. AI does not change the fundamentals as much as you would think. Why you choose a database still matters. It might not be because it has the best documentation or marketing or some sales guy brought you to dinner. But a database, for example, they're all fundamentally the same technology but they're all optimized for different use cases. So the flaw in this logic is being too abstracted and thinking too much of this stuff is the same. It's not. And there is a good reason for good quality code and there's a reason for bad quality code in certain domains. AI is pushing things to such an incredible pace that you realize the good principles are required. The diligence is required. AI is going to drive the need for more smart individuals. More skilled individuals.

The PM playbook was built on an assumption that the technology underneath your product is roughly stable With the current pace of model progress, this is no longer true. Here's how we've evolved the PM role:

Heroku 2.0

MCPs are the opposite of dead. They are the life blood of how AI agents use services inside mid-sized and above companies. Case in point: Uber runs on MCPs internally, for good reason. Details: newsletter.pragmaticengineer.com/p/how-uber-use…

There's a lot of noise around how "Ai generates buggy software". The truth is writing the code was always 20% of the time. Testing and refining was always 80%. But now as that 20% compresses 10x, we want to compress the 80% as well... That's the mistake.

I was a 10x engineer. Now I'm useless.

🚨BREAKING: Berkeley researchers spent 8 months inside a tech company watching how employees actually use AI. The promise was simple: AI will save you time. Do less. Work smarter. The opposite happened. Workers didn't use AI to finish early and go home. They used it to take on more. More tasks. More projects. More hours. Nobody asked them to. They did it to themselves. The researchers sat inside the company two days a week for 8 months. They watched 200 employees in real time. They tracked work channels. They conducted 40+ interviews across engineering, product, design, and operations. Here's what they found. AI made everything feel faster, so people filled every gap. They sent prompts during lunch. Before meetings. Late at night. The natural stopping points in the workday disappeared. People ran multiple AI agents in the background while writing code, drafting documents, and sitting in meetings simultaneously. It felt like momentum. It felt productive. But when they stepped back, they described feeling stretched, busier, and completely unable to disconnect. 83% said AI increased their workload. Not decreased. Increased. 62% of associates and 61% of entry-level workers reported burnout. Only 38% of executives felt the same strain. The people doing the actual work absorbed the damage while leadership celebrated the productivity numbers. Then came the trap nobody saw coming. When one person uses AI to take on extra work, everyone else feels like they're falling behind. So the whole team speeds up. Nobody formally raises expectations. But the new pace quietly becomes the default. What AI made possible became what was expected. The researchers gave it a name: workload creep. It looks like productivity at first. Then it becomes the new baseline. Then it becomes burnout. AI was supposed to give you your time back. Instead it's eating more of it. And the worst part? You're doing it to yourself. Voluntarily.

Anyone and everyone working in security engineering or caring about security have their work cut out for them We’re so early in AI agents pushing code to prod without human intervention - but prompt injections are already spreading like wildfire. Infecting high-profile projects

Con esto de la IA y el Spec-Driven Development, mucho dev por fin ha conocido el Documento de Diseño de Software. Están por fin descubriendo una ingeniería que nació en los años 60s.

Ahhhh, Codex 5.3 (xhigh) with a vague prompt just solved a bug that I and others have been struggling to fix for over 6 months. Other reasoning levels with Codex failed, Opus 4.6 failed. Cost $4.14 and 45 minutes. Full trace plus includes original issue: ampcode.com/threads/T-019c… I know this prompt is relatively bad. Honestly, our stable release is in a week, and I was throwing some Hail Marys at the frontier models to see if I could get a clean, understandable fix for some of these bugs. By using `gh`, it grabs much better context from the issue, so its not terrible. The best thing that Codex did was eventually start reading GTK4 source code. That's where I ended up (see my GH issue), and I knew the answer was somewhere in there, but I didn't have the time or motivation to do it myself. The other models never went there, and lower reasoning efforts with 5.3 didn't go there either. Only xhigh went there. I think that was a critical difference. The final fix was decent. It was small, all in a single file, and very understandable. It had one bug I identified (you can see in the trace), and then I manually cleaned up some style. But, it did a great job. Definitely an "it's so over" moment. But at the same time, it feels amazing because now our next stable release will have this fix and I was able to spend the time working on other fixes as it went.

Santa came really early this year 🎉 Free Open Source Software for the Win!

Fabric8 Kubernetes Client 7.6.0 is out! 🎉 ✨ Kubernetes 1.35 (Timbernetes) support ✨ New Vert.x 5 HTTP client implementation ✨ OkHttp upgraded to 5.3.2 🐛 TLS, timeout & type erasure fixes 📖 blog.marcnuri.com/fabric8-kubern…

@0xmitsurii Always has been a hobby, a well paid hobby 😉

Clawdbot CEO: Programming isn't a career anymore. It's a hobby.

@RikNieu github.com/containers/kub…

MCPs that rocks • GitHub CLI (gh) • CodeGraphContext • Context7 MCP • Docker MCP • Firecrawl MCP • Jina Reader MCP • Figma MCP • Browser DevTools MCP Any others?

@iagolast Yo diría que esa es precisamente la ventaja competitiva cuando quién implementa el código de producción es una máquina. 1. Implementa los tests. 2. Implementa el código 3. Revisa 4. Refactoriza, descompón y desacopla 🚀🚀🚀🚀

No se si la arquitectura y el testing seguirán siendo una ventaja competitiva mucho tiempo. Diría que este es el último año.

La inteligencia artificial ya no "ayuda": ahora empieza a despedir enriquedans.com/2026/02/la-int…

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

If you pay attention he said AI will write all the code (which is happening at Anthropic) and never said they won’t need software engineers. Turns out software engineers prompting the AI results in much better software, and software engineering is a lot more than writing code!

Started a coding agent from my phone during a coffee break. Reviewed the finished PR from my workstation an hour later. Wrote up how I built the dashboard that makes this work: blog.marcnuri.com/ai-coding-agen…

coming soon in @goose_oss: MCP Apps can inherit styles