dunreith

While I'm glad that I can read what someone is talking about on X/Twitter without giving away my privacy, I'd much rather see a trend of moving off of the platform altogether (or at least posting to multiple platforms to make the transition off of X more mainstream palatable)

All of these layoff announcements, regardless of high profits or otherwise, are quickly eroding any sense of loyalty I have toward my company - and it should do the same for all of the tech workers out there.

You have to do what's best for you and those that you support. Do not accept anything less; your company certainly will not.

Until it becomes apparent that the constant turnover of tech workers hits the bottom line, these companies will do less than nothing to make things better for their employees.

At the very least, it would be nice to have an easy-to-consume standard high-level infographic. Take the "Nutritional Information" table that's been standardized on the side of most American foodstuffs. If we could get Terms of Service with a table at the top with the most important info standardized, it would go a long way.

the Secure Information Technology Hub™?

It's honestly not a bad idea, just a bad implementation. I use shadow.tech to achieve this and they do it well - instead of giving you game-specific VMs (or whatever Stadia is), they just give you a gaming VM with Windows and you install your own Steam / Epic / GOG / XBLive whatever on it.

Fortunately not, but we're deploying the frontend for an eCommerce site so we don't deal with (much) data can could be corrupted.

I suppose there's an even larger scale that the law of large numbers applies and you can more reasonably filter out "the noise"

> incorrect thinking that the way to reduce bad outcomes from software is to change it less often

This. So much this. The way you turn a bug into a "bad outcome" is to make it slower to change. If you can deploy quickly and easily, you can fix any software issue before it becomes a big problem.

I'm currently at a Fortune 500 and we're doing CD for our eCommerce site. I count myself very lucky to have been involved in the process.

> As long as you have manual processes, it's not continuous.

Agreed. I'm all-in for Continuous Deployment. Continuous Delivery is a half-measure at best.

I led our team to a full CI/CD (Deployment) and while it felt really counterintuitive to move quickly and have the occasional bug show for our customers, the speed at which we could fix the bug has vastly offset it. Introduce a bug? Fix it same day. Introduce a breaking change? Rollback and fix it. No biggie.

Depends on which CD you're talking about. Continuous Delivery: artifacts get delivered and are ready to deploy when someone is ready to do it. Continuous Deployment: built artifacts get deployed automatically.

A SQL developer walks into a bar. He walks to two tables in the back and asks, "mind if I join you?"