We already do with tidal generators.

And theres ways to follow currents for extra help, but you’re limited to that and where the current moves.

Anything else and you’d have to violate the laws of physics.

It’s like putting a wind turbine on an electric car. The increased drag would cost more electricity than the turbine could produce.

It’s kind of funny to see all these headlines not long after everyone was going on about Apple not doing enough with AI and going to slow with their rollout.

They have just done it a lot smarter than the others. Not rushing out to throw piles of money at something. Same thing they did during the pandemic, when other companies were massively overhiring trying to ride the wave. Apple didn’t and subsequently hasn’t needed to hold massive layoffs.

Because it provides zero practical benefit for the vast majority of people.

There’s no reason to other than to be the same as everyone else, and we already are for anything scientific or medical.

Also, the marathon is only a tiny part of the story, and the very end.

Pheidippides first ran from Athens to Sparta (150mi) to seek help for the battle, then immediately back to Athens, then fought in the battle of Marathon, then ran the 25 miles from Marathon back to Athens to announce the victory.

Focused on private groups of friends and family

So, a group chat.

the future of social networking lies in small, private communities powered by messaging, photo sharing

So it literally is just a fancy group chat. Or I guess a singular feed of multiple group chats…

Ehhhhhhhh.

We have two Kias. An EV6 and a Telluride, so their EV and gas lines.

They’re nice looking cars, but the “Kia quality” definitely creeps in. If we didn’t get them on dirt cheap leases I would probably be pissed lol.

No I got that. I’m saying that by the time the prod deploy comes around, there’s no proofreading left to do anyway.

Not proofreading texts should have zero bearing on being able to write and deploy software because it should be proofread several times before the actual prod deployment. Hell it very likely isn’t even the same person doing the deployment that wrote the code.

Yeah that’s what the MRs are supposed to be for. To catch those and proofread.

There shouldn’t be any changes at all from the last test to going to production though. Even cleaning up comments.

Code should ideally be going through tests before prod anyway. There should be no code changed from successful test to prod. Proofreading shouldn’t matter at that point. Just scheduling the actual deploy.