How to uncover hidden complexities in your software stack

Every engineer fears the "unknown unknowns." Systems fail not because of what we know, but what we don't even realize we should be looking for. The key to high-performing software isn't just reacting to alerts; it's building frameworks that actively surface those hidden complexities. It's time to illuminate the dark corners of your stack. 🔦 Listen to New Relic's Nic Benders on the Stack Overflow Podcast to learn more. #Observability

A common challenge in software development is creating and maintaining robust development environments. The rise of AI agents has amplified this complexity by adding new demands around permission controls, environment isolation, and resource management. 🎙️ Listen to this podcast in which our CTO Chris talks with Kevin Ball about Ona, the impact of coding with parallel agents, the future of IDEs, choosing agent-friendly languages, code review as a new bottleneck in the software development lifecycle, and much more. Link in comments 👇

Coding Chats has reached episode 50! In this episode Lou Franco and John Crickett technical debt, its implications for software development, and the importance of quantifying it. Lou argues that technical debt is not just a financial metaphor but a real issue affecting developer productivity and team dynamics. Their discussion covers the role of managers in understanding and addressing technical debt, the importance of metrics, and the eight questions that can help teams evaluate their technical debt. Additionally, the conversation touches on the impact of AI on technical debt management, highlighting both its potential benefits and challenges.

“Coupling is an inherent part of system design, not something that is necessarily good or evil.” A fresh perspective on a fundamental software design concept from Vlad Khononov, Creator of the Balanced Coupling model, on Tech Lead Journal, Episode #188. Instead of viewing coupling as universally bad, the conversation explores how to balance it intentionally to build truly modular and maintainable systems. ⤷ Watch the full episode here: https://lnkd.in/gYqwAwTR ⤷ Check out the show notes for all resources: https://lnkd.in/dM4kvXEV #TechLeadJournal #SoftwareDesign #Coupling #Modularity #SystemDesign

In the delusion of solving problems, humans often create more harm than good. Big cities gave us the illusion that the planet is overpopulated while countries like Mongolia sit 99.7% empty.  We didn’t solve the food problem we industrialized it.  We didn’t invent green energy, we subsidised it at the cost of olive trees that outlived empires. And technology? Same pattern, just wrapped in marketing. When I started, I wanted to code in C, maybe even build operating systems.  But “memory-safe” languages were the new salvation. Everyone said "Forget C, learn Java or C#." Years later, I learned that knowing C made me dangerous, because I actually understood what was going on under the hood. Even when I didn’t have to `free()` memory. Fast forward 19 years, and I’ve seen every "next big thing" come and go:  🧱 Java, C#, Python now Go, Rust.  🧩 No-code platforms.  ☁️ The "cloud."  💫 And the never ending promise that this language or that framework will fix everything. Here’s the truth:  I’ve spent years building and fixing other peoples code, then auditing projects many of them in "memory-safe" languages and most of the security flaws I found have nothing to do with memory.  They come from ego, ignorance, and lack of focus. We built a culture of hobbyist developers with massive egos, convinced their half working webapp is the Mona Lisa of software.  They know 10 languages, master none.  They patch bugs with libraries they don’t understand.  And when things break, they say, "Isn’t that the garbage collector’s job?" We replaced craftsmanship with convenience.  Discipline with dependency.  Understanding with abstraction. So no Rust, Go, Java, Python, or whatever comes next won’t save us. Because the problem was never the language.  The problem is the developer. Everyone’s in a rush, and rushed dogs have hairless puppies. 🐶 🎙️UndefinedBy0x4E — Episode 20: The Illusion of Progress  👉 https://lnkd.in/dGnUAQFa

Code complete is a famous reference among software engineering circles for its quality content and I haven't read it yet. However, it is worth listening to this episode of The Pragmatic Engineer podcast by Gergely Orosz . Covering several topics, from technical excellence to career planning and ventures into management by technical people, it emphasizes that the fundamentals haven't changed much in all those years since first edition. #softwareengineering #softwaredevelopment #programming #career #lifelonglearning https://lnkd.in/d_NZcXBz

The most profitable question in DevRel: "What happens next?" Most quickstarts end with "Congratulations! You've sent your first API call." Cool. Now what? Three clear paths: - Build a real project (with tutorial) - Explore advanced features (with examples) - Go to production (with checklist) That one addition increases your 30-day retention by A LOT! Developers who succeed once want to succeed again. But only if you show them how. Your job isn't done at "hello world." It's done when they're in production. --- Hi 👋 I'm Marcos, I run DevRel Bridge where I help developer-first companies scale faster with strategy, content, and community. If you found this useful, you'll probably like what I post here.

Welcome to Vibe Code, the thought leadership series where good vibes meet groundbreaking code. In our debut episode, Jamie Burgess dives into the evolution of AI-driven development and explore the rise of vibe coding – a term coined by Andrej Karpathy in 2025 that’s reshaping how we build software. https://ow.ly/nC2050X9isS #VibeCode #AIDevelopment #GenerativeAI #InnovationSeries #FutureOfCoding

“Like most ops teams – overloaded, lots of work, always behind the power curve.” That’s how Jesse Ford describes life before orchestration. Then came the shift: combining Ansible, APIs, and Python into one orchestrated workflow changed how his team responded, scaled, and innovated. 👀 Curious about the details of his full automation journey to get there? Keep an eye out for a new Packet Pushers podcast dropping Friday.

What do #observability leaders have in common? A top-tier tech foundation that drives high ROI and includes: ✔️ OpenTelemetry ✔️ Code profiling ✔️ Observability-as-code But that's not all! Our own Patrick Lin breaks down key findings from our State of Observability 2025 report on #SplunkBlogs. 👉 https://splk.it/3JjbjmM #SplunkO11y