Operations | Monitoring | ITSM | DevOps | Cloud

DevEx Talks ep 6 - Working Neurodivergent: What Helps, What Doesn't

In this episode, we explore neurodiversity in tech and beyond with guests Carl Alexander and Zach Stepek. They share firsthand experiences of what has helped them thrive as neurodivergent professionals and what has not. Together, they discuss the importance of community as a key factor in empowerment, growth, and long-term success for neurodivergent individuals in both work and life. PlayList Resources for Further Learning.

AI Agents Write Broken Code 49% of the Time #speedscale #AI #Coding #Tech #DevOps

AI agents write broken code nearly 50% of the time. By adding a traffic-based deterministic evaluation, Speedscale boosted unsupervised bug-fixing quality from 51% to 77% in just 5 minutes. This helped slash token costs and eliminate rework without human intervention. Learn more: speedscale.com.

Harness Agents

Today, we're launching Autonomous Worker Agents, AI agents that run as governed pipeline steps inside Harness. They inherit OPA policies, RBAC, audit trails, and scoped credentials from the first run. And because they live inside your Harness pipelines, they reason using the Harness Knowledge Graph: your services, deployments, incidents, and policies.

A Four-Step Blueprint for Faster Root Cause Analysis: A Logz.io Webinar

Incident investigations take so long not because the fix is hard, but because finding the right fix is. Most engineers spend 20 to 60 minutes just understanding what’s wrong before they can act, not fixing anything, just trying to see the full picture. The framework that changes this has four steps: Orient, Isolate, Hypothesize, and Verify, and the order matters more than the tools.

The most dangerous window is before threat intel knows about it

When a malicious package is first published, threat intelligence sources haven't flagged it yet – and every team pulling from a public registry is exposed during that entire window. The fix isn't faster scanning; it's a policy that holds new packages for a defined cooldown period before they're eligible to pull. By the time the window closes, the threat intelligence has caught up. Teams pulling direct from npm or PyPI have no equivalent enforcement layer – which is exactly how attacks like Shai-Hulud got in.