Agent-driven development looks fast.
But here’s the problem: code is getting cheap. Confidence isn’t.
I’m seeing teams ship more, test more, generate more — and still lose control over architecture, quality, and long-term maintainability.
This is not a tooling problem. It’s a standards problem.
https://www.the-main-thread.com/p/agentic-sdlc-java-teams-trust-quality-standards
Last Call zur Mastering Observability: OpenTelemetry, KI und Agenten-Systeme
Die Online-Konferenz zu proaktivem Reliability Engineering, Agentic Observability und KI im SRE. Jetzt noch Tickets für den 16. April sichern.
The future of cloud cost management is here.
From Pay-As-You-Go to Pay-As-You-Use, this deep dive explores how AWS can evolve with real-time cost autopilot, AI-driven FinOps 2.0, and autonomous cloud optimization.
Cut waste. Predict spend. Automate everything.
Read more: https://shorturl.at/sKCpZ
#FinOps #AWS #cloud #CloudCostManagement #DevOps #AIincloud #CloudOptimization #Tech
24 hours until the CfP for "IaCConf" closes: https://docs.google.com/forms/d/e/1FAIpQLSeY6-IlyYXSauF8Dg9cs7fHGKiSJqTcecdk_ARXOKHj6HNN6w/viewform
Event Date: Thursday May 14, 2026 Format: Virtual, 40 minute session (30 minutes content, 10 minute Q&A) Submission Deadline: Tuesday April 7, 2026 About IaCConf & IaCConf 2026 IaCConf is the community dedicated entirely to Infrastructure as Code (IaC), bringing together DevOps, platform engineers, and infrastructure leaders to focus on real-world, practitioner-led discussions. IaCConf 2026, being held May 14, 2026, is the second annual virtual event consisting of 15-20 sessions. Session Type & Duration Each of the sessions for IaCConf 2026 will be 40 minutes long, comprised of a 30-minute presentation with 10 minutes of live Q&A. IaCConf 2026 Theme: Keeping Pace Software development has entered a new era of velocity. Developers are shipping faster than ever, driven by AI-assisted coding, automation, and modern delivery practices. But while development speed has accelerated dramatically, platform and DevOps teams are still accountable for uptime, security, governance, and compliance. IaCConf 2026 is looking for real-world, technical talks that explore what happens to infrastructure, workflows, and guardrails when velocity increases beyond what existing systems were designed to handle. Suggested Themes & Areas of Interest The following SIX themes represent the kinds of stories and technical experiences we’re especially interested in for IaCConf 2026. These are not formal tracks, and talks don’t need to fit neatly into a single category: 1) Keeping Pace with Developer Velocity Enabling fast-moving development teams without increasing operational risk How teams adjusted guardrails once velocity exposed real risk Platform patterns that scale with modern delivery speeds 2) Infrastructure as Code at Scale Managing IaC complexity as environments, teams, and velocity grow Preventing sprawl, drift, and inconsistent patterns across large estates Lessons learned from mature IaC implementations 3) Governance, Security, and Control Using policy, automation, and controls to enable teams to move faster Policy-as-code in real-world environments Balancing autonomy and accountability as scale increases 4) Platform Engineering in Practice Platforms shaped by real usage, not just design documents What changed once platforms were stressed by real teams and real scale Measuring platform impact through reliability, risk reduction, and operational load 5) Slowing Down to Move Faster with IaC Using IaC to regain predictability as delivery speed increases Trading short-term friction for long-term safety and throughput Migration stories where control mattered more than velocity 6) Leadership & Organizational Pressure Leading platform teams under increasing delivery pressure Managing responsibility when things go wrong Aligning incentives between development and platform team Guidance for Submissions IaCConf is a practitioner-first, community-driven event. We prioritize talks grounded in real infrastructure, workflows, and operational constraints. Strong submissions: Are based on real-world experience, based on systems used in production Share concrete lessons learned, not just theory or best practices Respect the audience’s experience and avoid oversimplified solutions Vendor-neutral talks are preferred. If tools are discussed, they should support the story, not replace it. If you’ve wrestled with the challenge of keeping platform teams effective in a world of accelerating software delivery—and have lessons worth sharing—we invite you to submit a proposal and help the community keep pace together.
I was running some AWS CLI commands today and found this string in the output:
"AccountCreatedDate": "2015-03-11T15:06:45Z"
I completely missed the 11-year anniversary last month. Since I was born in 1995, I was only 19 when I opened this account. It is wild to realize I have been tied to Big Tech infrastructure for over a third of my life without really thinking about it.
Back then, the cloud felt like the ultimate solution.
But today, my main goal is to move away from it. Funny how the background processes of our digital lives can run for over a decade before we finally audit them.
#AWS #BigTech #SelfHosted #HomeLab #Privacy #TechPhilosophy #Blog #Thougts #Devops
Kubernetes "self-healing" is a dream until it hides a production-melting bug in plain sight.
I’ve just posted about moving beyond silent restarts with Grafana and Telegram alerts
Read more: https://stuartgreig.dev/blog/monitoring-kubernetes-pod-restarts-with-grafana-and-telegram
SourceHut was disrupted by a DDoS attack. Over the holidays SourceHut experienced a DDoS attack primarily targetting git.sr.ht. For a period of several hours we experienced severe performance issues and intermittent outages as a result, primarily affecting git.sr.ht. Our upstream network provider identified the malicious traffic and blackholed the appropriate routes, but due to a configuration error SourceHut’s AMS subnet was entirely null routed for a period of about one hour yesterday, causing a complete outage for all services. Once the configuration error was corrected, the DDoS continued to cause performance issues that primarily affected git.sr.ht, until the attack died down later yesterday afternoon.
Anthropic accidentally leaked 512,000 lines of Claude Code's TypeScript source; what does it reveal? Plus: Iran targets US tech companies, California's AI executive order, Microsoft's worst quarter since 2008, and more.
Markus Eisele
heise Developer
Ismail Kovvuru
Calling all papers
Leanpub
Dima
Stuart Greig
r1w1s1
Chris Short
PSConfEU