I like to shoot for the middle ground: skim for key functions and check those, run code locally to see if it does roughly what I think it should do and if it does merge it into dev and see what breaks.

Small PRs get nitpicked to death since they're almost certainly around more important code

We had a zoom call with a very well reviewed, recommended broker local to us. Next day I get a spam call pretending to be the bank we talked about the most as a lender, but that we currently have no business with. My paranoia has been at 100% ever since

Assuming a ground clearance of 10cm, and a wheelbase of 2.4m (source: my ass) then you can construct an arc under the wheels

This arc says you could drive such a car on an earth with radius as small as 7.25m. Actually, it could be slightly smaller because of where the wheels would contact, but I've lost interest

I may be dumb about this stuff but what is an SPF? How does vit c boost it?

Outlasted 4 and 1 - charles hasn't died yet

Most people (even with otherwise good understanding of tech) still fail to grasp that "an NFT" is not the monkey picture itself.
This is both why some managed to be bought for insane prices, and why we see reporting like this.

Your examples would actually be a useful case for NFTs since you'd have to both have a genuine card, and the token saying its genuine

I've been trying to get my local council to enforce the law on the road near me and have just been fobbed off repeatedly.

It's a 30 road, with a school and loads of pedestrians and cyclists using it yet we see people running the red lights, speeding well over 50 and doing crazy overtakes DAILY

I've driven and cycled in 3 other countries and England is by far the scariest, feels like every other driver is trying to kill you

I think most of the horror stories are from people printing way too fast and too low
Many people print with too small z-offset because "that's when it sticks". you can get away with it in pla but petg will just become a mess

It's not stateless end-to-end, it just means the client needs to keep track and pass the state rather than drivers or hardware

I'm not 100% on the motivation but from an architectural standpoint it does make sense - your software can now do many new and weird things without a hardware change

One example I saw was allowing an arbitrary number of streams to be processed simultaneously, just passing the different context state for each stream

For me it's the acceleration and speed they don't comprehend.even "safe" collaborative robots can accelerate to huge speeds in the blink of an eye, and being electric they'll do it at maximum force

I've driven one into my head before and its remarkable how soft it was thanks to the tech involved but movies miss the fact that if it wanted, even a small arm could have gone through me

If you ever work on a modern industrial system then you'll see all kinds of rules, safety measures and more fun

It often makes small jobs extremely tedious, but I always remind myself it's because the robot arm I'm looking at is strong enough to throw me across the room or crush my bones.