Organizations are constrained by human and systems-level problems. We remain skeptical of the promise of any technology to improve organizational performance without first addressing human and systems-level constraints.
We remain skeptical and we remain human.
—Kent Beck, Laura Tacho, and Steve Yegge
Geopolitics is driving infrastructure decisions: with the US no longer seen as a reliable partner, European organizations are actively reducing dependency on American cloud providers and US-controlled software. European organizations are starting to treat US dependency as a risk to be mitigated, not a convenience to be accepted.
Yes, I’ve enjoyed the ride from ops/sysadmin to devops to SRE. It practically doubled my salary. But “ops” pride never went away. Ops is what we do. Someone still needs to understand why the pods aren’t scheduling, why latency spiked at 3am, and how to make deploys boring. Great article form Charity Majors.
Maybe that’s the whole point: you don’t need to justify having your own corner of the internet beyond “I like having my own thing”.
I’ve always liked how Daring Fireball did this. Simon Wilison’s post inspired me to do it for my own blog as well. Maybe this way it can get some more content. :o)
(Originally posted on our company blog Silverfin Engineering) After attending DevOpsDays Amsterdam for what must be the seventh or eighth time, I can confidently say it remains one of my favorite conferences in the industry. The event’s unique combination of workshops, single-track talks, and Open Spaces consistently delivers valuable insights that I apply throughout the year. The balance between technical skills and interpersonal capabilities (often the more challenging of the two) makes this conference particularly valuable. ...
The Problem with Traditional Development Workflows Our traditional SDLC doesn’t make a lot of sense anymore now, does it? Whether you’ve read Accelerate and are a “high performing team” doing trunk-based development, or still stuck in GitLab flow or GitHub flow, once you’ve drunk the agentic Kool-Aid, it becomes apparent these will no longer cut it. This is due to a couple of reasons. For starters, since we’re now “orchestrating”, should reviewing be shifted left earlier in the process? And what about actual PRs, when you’re already reviewing code in real-time with AI (like pair programming), does the traditional post-hoc review still add the same value? ...