How many libertarians were involved in the decisions that yielded this situation again?

That's a valid approach for sure. What I've found in that case, however, is that taking Ops out of the loop and relying completely on developers for operational response to an incident in production yields poor results. Put simply, it's not their core competency, and most don't take to it well (although some do!). It's a very different type of pressure to which they're unaccustomed.

In my experience, a hybrid approach is best, where Ops personnel quarterback a production incident (or Support, assuming it's a mature org), and escalate as needed to development.

YMMV

You sound like you're referring to corporate IT throughout your comment, or at least that's my impression. DevOps concepts don't really apply there...or at best it's a square peg in a round hole situation.

Building custom software, and more specifically SaaS, truly do have a lot to gain by adopting DevOps, especially when combined with Agile development.

From the article:

Wow. I get ditching DST, but make a call one way or the other across the board. This will get messy..

Interesting. To be fair, I only ever had their internet service after cutting the cord years ago, and handled my own wifi. The price was around 50/mo for years, and they periodically doubled my speed for free.

I had Grande service for years, and they were by far the best internet provider I've ever had. Low and consistent price, and rarely any connectivity or speed issues.

I recently moved to an area they don't service and am stuck with Spectrum...which has been a horrible experience all around. This article makes me miss them even more.

Agreed.

I disagree. If I use Keepass and store my DB locally, then I'd argue that's more secure than anything stored in the cloud. At the very least, it's up to me to ensure it's secure, rather than hoping someone else is doing so for me.

This doesn't require cloud storage of passwords.

Or, store it COMPLETELY client side...and encrypt it.

So you propose using a cloud storage service for passwords, unless you're banking?

Many of those "crying about it" never signed up for Facebook in the first place...yet Facebook keeps data on them anyway.

Measure key metrics like cycle time, quality (bugs), code coverage, test stability, and escapes. Review weekly as a team, however small that may be. You generally don't optimize or improve what isn't measured and regularly reviewed. Release small changes often rather than big changes less frequently, and automate as much of the release process as possible.

This stands out in this day and age. I'm glad you've successfully introduced peer review, but I haven't heard of a shop in the last decade that doesn't implement peer review. Sounds like a change at the top is needed if you're at a shop that far behind.

Hang on a second, what did Perl do to deserve getting pulled into this? Everything else was spot on, but that's taking it too far!!

I was going to mod you up, but that last link is useless in the context of this conversation. My home town of 10k people in the middle of the midwest is on it..

You come off as pretty dumb defending this..

Then say neither agree/disagree, and simply express your opinion. The double negative in question is never appropriate (imo).

In that case, just say "I agree, but"

/petpeeve