MajorHavoc @ MajorHavoc @lemmy.world

Posts

2

Comments

996

Joined

2 yr. ago

Besides the dual stream confirmation in Discovery, I believe it's in Enterprise that we first learn that Klingons have two of every organ.

And I believe I recall a throw away line of confirmation (of the double organs) in Picard.

I'm honestly surprised if Lower Decks hasn't dealt with the topic yet.

Yeah. The interesting money seems to be on Thor. Could break either way. Place your bets everyone.

There's a lot of generosity toward Thor in this thread. And I think that's great.

Even though he's going to rule Asgard someday, while his brother is clearly more qualified. /s

Yep. That's actually what at least one version of Reed Richards does with the gauntlet.

Good point, technically. But... We all know Thor would be gone. There's no way the rightful heir to the throne of Asgard is in their top 50% intelligence.

And given that they'd be at full strength they'd probably find a way to stop him and reverse things faster than they did in OTL

Good point. But I dunno. Thor is a big power loss, and unless Captain America gets a free pass for emotional intelligence counting, they're short in leadership, too.

And that's why Thanos should have made everybody half as large as they once were.

Holy cow. However intelligence is defined, you're smarter than I am. That would have been a really short film.

...and I'm just realizing that universe would look pretty much exactly like those little kid Marvel Adventures shows...

I honestly fail to see the difference between "don't deploy on Friday if this can wait until Monday" and "don't deploy on the evening if it can wait until the next morning".

Both are top tier practices.

If your team is used to ship frequently and incrementally, it won't matter when you ship and your risk will always be small."

Yep. That's all great advice.

But I'm just a veteran saying that all the preparation in the world doesn't compare with simply not inviting trouble right before the evening or the weekend.

Organizations that feel that they desperately need to take that risk, are doing it because they disrespect their team's time.

It can be the smallest risk in the world, but it's still a risk, and it's a completely unnecessary one (outside of an active in progress disaster recovery).

Again: if the changes are small enough and you have automated checks in place, they should not require manual intervention.

You've used the magic word "should". "Should is famous last words." The trick to keeping developer talent is not to risk the developer's weekend plans on "should".

And yes, maybe I'm only risking our cloud ops person's weekend plans. Same principle applies.

Every change that isn't already an active disaster recovery can wait for Monday.

Good question.

Since we're doing a deep dive, I'll share some additonal context. I'm the manager of the developers. On my team, that means the call comes to me first.

I have had Thursday deploys that resulted in bugs discovered on Saturday. Here's how the conversation on Saturday went:

"Thanks for letting me know. So we didn't notice this on Friday?"

"No, it's subtle." Or "We noticed, but didn't get around to letting you know until now."

"Okay. I'll let the team know to plan to rollback at 0900 on Monday, then we will start fixing any damage that happened on Friday, and the weekend."

That mite bee! I will cheque!

It's not about how hard the problem is to reverse, it's about respecting the team enough not to call them on Saturday.

It dosent have any mispelings.

XML

Only inexperienced developers* are unafraid of deploying right before leaving the office.

There's an entire untapped universe of possible new ways that things can go horribly wrong.

*Experienced developers who hate their boss and their colleagues, too, technically.

Now that's a team that knows what they're doing!

If something goes wrong, devs have to give up their weekend to fix the issues, leading to burnout and dissatisfaction.

Correct in spirit, but the words "burnout" and "dissatisfaction" are weasle words that spinless middle managers use.

The correct terms are "abruptly quiting without notice leaving the company fucked and our stock worthless".

A minor point, but worth clarifying.

I named most of them Marlin Jr, and Coral Jr, but I guess we can name one of them Nemo.

I'd think most PC games and other desktop GUI software runs on windows and looks like it runs on windows.

Right.

Most PC games currently run on Unity, which doesn't care whether it's running on Linux or Windows. I'm not aware of whether PlayStation runs a Linux kernel, but I would bet it does, since they wouldn't get a good price from MS on OS bulk licenses. When the game is installed on a Windows PC, it's obviously running on Windows. When a game is on any of the various (non-Microsoft) game consoles, odds are it's actually running under a Linux Kernel.

And I'd imagine that a web browser on windows isn't secretly a Linux environment.

True. I would argue that's running half on Windows, of course. The other half, the server, had about a 99.7% chance of being Linux, today. Mostly Amazon Linux running in AWS. Even websites recently developed entirely on Microsoft libraries, and served in Microsoft's cloud service Azure, are largely running under a Linux kernel.

What are some places that don't look like Linux but actually are?

Amazon Lambda, Azure Automation, GitHub Actions, Amazon CodeDeploy, Azure DevOps, anything Android (not GNU, but runs a Linux kernel), SteamDeck, almost every miniature gamesystem (Genesis Mini, PlayStation Classic, etc), and a variety of the smallest chips that usually run raw C code are gradually getting powerful enough to have a Linxu kernel (I E. Raspberry Pi Zero replacing Arduino in various recipes).

With the SteamDeck's recent rise here's also been a shift towards video games being written first for Linux, then cross-compiled for Windows and much later ported to Nintendo Switch.

I don't know if we have confirmation on whether PlayStation and XBox or Switch run Linux under the hood yet.

Switch almost certainly doesn't (or at least not a recognizable version) or we wouldn't see the release delays we currently see.

It seems like the vast majority of portable hardware above very low power stuff runs a Linux kernel now, even when the rest of the OS is unrecognizable. Mostly via Android, but in exceptional cases with a custom OS.