C++26 Adoption Decisions with Sandor Dargo

🔥 Claude Code authors 4% of ALL global GitHub commits in early 2026. Let that sink in. Spotify engineers haven't written code manually since December. Anthropic's own team ships 10–30 PRs per engineer per day — every one generated by Claude. This isn't the future. It's now. Here's how serious devs are actually using Claude Code 👇 ───────────────────── 𝗙𝗼𝗿 𝗗𝗮𝗶𝗹𝘆 𝗖𝗼𝗱𝗶𝗻𝗴: → Run "claude" in your terminal → It sees your entire codebase → Describe what you want in plain English → Review the diff, approve, done 𝗙𝗼𝗿 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴: → Paste the error + context → Ask: "What caused this and how do I prevent it from happening again?" → Not just a fix — a lesson 𝗙𝗼𝗿 𝗖𝗼𝗱𝗲 𝗥𝗲𝘃𝗶𝗲𝘄: → Claude Code Security dispatches parallel agents to scan your codebase → Found 500+ undetected vulnerabilities in real open-source projects → Severity-ranked. No patch without your approval. 𝗙𝗼𝗿 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲: → Paste your requirements → Ask Claude to propose 3 different architecture approaches with trade-offs → You make the decision. Claude does the heavy lifting. ───────────────────── The role of developer is shifting: ❌ Code producer ✅ Creative director of code The people building that intuition NOW have a structural advantage that compounds. What's your Claude Code workflow? Share below 👇 #ClaudeCode #SoftwareDevelopment #AITools #Programming #TechCareers #Anthropic

Spotify scaled to over 1 million automated code changes. 🎶 Managing thousands of components across millions of lines of code doesn't have to mean multi-month migration projects. At Code Remix Summit, Jonatan Dahl (Staff Software Engineer) and Sanjana Seetharam (Senior PM) from Spotify will share how they shifted to a fleet-first mindset with OpenRewrite and AI-powered background agents to run automated, daily refactorings continuously. Get your ticket ⤵️ https://lnkd.in/g5r2MUSJ #OpenRewrite #PlatformEngineering #DeveloperProductivity #Java

SPOTIFY SOLVED THE MICROSERVICES CHAOS PROBLEM. THEN OPEN-SOURCED THE SOLUTION Engineers wasted hours just figuring out what existed, docs were everywhere and nowhere, new hires spent weeks mapping the system before writing a single line of code so spotify built an internal tool to fix it then gave it to the world backstage is an open-source developer portal framework...it puts your entire engineering ecosystem in one place a software catalog that tracks every service, library, pipeline, and ml model with ownership, with status, with docs attached software templates so new projects start with your org's standards already baked in. no boilerplate debates. no inconsistent setups techdocs so documentation lives next to the code...engineers actually maintain it when it's not buried in notion or confluence spotify's internal chaos became a 32k star cncf project...1800+ contributors 4.5k companies running it in prod the tool that saved spotify's infra is sitting on github for free → https://lnkd.in/gq9yanir

I’ve seen a few comments lately suggesting OpenVerb is “copied” or “already exists.” To be clear: I built OpenVerb. It didn’t come from copying a repo—it came from a long development cycle where I was building real systems, running into the same limitations, and eventually designing a better execution model. I actually document a lot of that journey in “The Uber Year”—a period where I stepped away from a toxic work environment and went all-in on building. OpenVerb came out of that process. What I ended up with isn’t just another “AI tool.” It’s a deterministic execution layer: → Structured verbs instead of loose tool calls → Policy enforced at the action level → Clear execution lifecycle (validate → authorize → execute → receipt) And it’s not theoretical. I built PaywallOS as a working implementation—showing how this model replaces typical, fragile paywall logic with something structured and auditable. So if someone says “this already exists,” I’m open to seeing it—seriously. But it has to match the architecture, not just sound similar on the surface.

"That's where most AI-generated code falls apart, not because the AI is bad. Because the brief was." And that is why I am building the Spec System https://lnkd.in/eAD42MuQ

Day 2 of DSA. Showing up again. Here's what got done: ✅ DSA — Tackled number pattern problems. Nested loops are starting to feel less scary and more like a puzzle I actually enjoy cracking. Code: https://lnkd.in/dTMCJdkq ✅ Project (Moodify) — Ditched the Spotify API battle. Switched to Last.fm to fetch songs based on vibe, then hooked up the YouTube API to pull up the actual track. Progress. Repo: https://lnkd.in/diBxKnMj ✅ Computer Networking — Covered basics of transmission modes, network criteria, point-to-point vs multipoint connections, and broke down the pros and cons of star, mesh, and bus topologies. Following: https://lnkd.in/dTkJ6qRz Day 1 was the start. Day 2 is the proof. See you at Day 3. 🚀 #DSA #100DaysOfCode #BuildInPublic #ComputerNetworking #DevJourney

A Lesson From Production Systems 💡 One thing production systems teach you very quickly: 👉 Code that works locally doesn’t always work in production. Because production comes with realities you can’t ignore: • Real users 👥 • Real network conditions 🌐 • Real scaling challenges 📈 It’s in production that assumptions break, edge cases appear, and true engineering begins. That’s where you stop just writing code… and start thinking like a backend engineer. Happy New Week 🚀

Spotify's engineers haven't written a single line of code in months. That's not a warning sign. That's a signal. Their internal system "Honk," integrated with Claude Code, allows developers to describe what needs to be done — and the AI builds it. A fix committed on the commute. A feature shipped before the developer reaches the office. 50+ new product features delivered in 2025. The same team. A fraction of the time. The conversation this sparked — "are developers becoming obsolete?" — is the wrong question. The right question is: what does engineering look like when the bottleneck is no longer writing code, but knowing what to build? At Intellova, this is exactly the shift we're building for. AI doesn't replace engineering judgment. It amplifies it. The teams that understand this will move faster than anyone thought possible. The teams that don't will wonder what happened.

Quote of the day : "Coding agents are starting to write production code at scale. Stripe’s agents generate 1,300+ PRs per week. Ramp attributes 30% of merged PRs to agents. Spotify reports 650+ agent-generated PRs per month. Tools like Claude Code and Codex make hundreds of API calls per coding session, each carrying the full conversation history. Behind every one of these workflows is an inference stack under significant KV cache pressure." https://lnkd.in/d5WueCFw #nvidia #Dynamo

How do you pair on‑device AI with a production‑ready UI? This livestream shows how to combine Qt (QML, Qt Quick) with the Qualcomm AI Stack to build edge AI apps on Qualcomm Dragonwing IQ9 EVK, end to end. Qt Group Staff Software Engineer Tinja Paavoseppä joins our open source advocate Rain Leander to break down real workflows, tools, and integration patterns for shipping AI‑powered applications on device. 📺 Tune in on March 31 | 9 AM PT · 6 PM CET: https://bit.ly/41Gvb8E