coolcase

> I'm going to guess that you're a really good shape that a 2 km walk isn't a big deal, but I don't think most Americans can do that.

Shit that's horrifying.

I have health issues and walking 2km a day to try to help fix. So I see 2km a day as basic. 6-10km run a day would be "fit" IMO. things as humans are designed to walk.

Living in suburbia means I have to walk "for the sake of it" although I cam make it useful e.g. get some milk!

As for cold. Anything above minus 5 should be OK just wear stuff like skiiers wear which can be got cheap off brand.

Should be budgeted though right.

No mystery really.

Looks like the 72/90 is actually from shadow banning.

But to answer whose opinions do you want to ban? Who is speaking correctly?

Thanks. So sounds like the same machine should run the same calculations and get the same results each time, but differences may appear between machines.

Startups might be the new SDE1 while trying to do stuff outside of capitalism might be the new startup.

Not in terms of financial reward of course. But in terms of rewarding career off the beaten path.

Personally while I want to do a startup I am finding the boring path you mention quite fascinating!

25Mhz to 33MHz. Oh yeaaaaaaa!

Do you have any feeling as to why it only lasted 4 months. Sounds unusual to have the spot on CFS like experience for such a short time so wonder if there was a trigger to recovery.

Root causes I suspect. The problem of a syndrome.

Was a root cause done on that? Was it due to wind power?

Wouldn't mind some bird mitochondria!

Thanks! So machine differences in their FP units drives the entropy, and the code doesn't handle that when picking eigenvectors?

It is good for ballparking. PR count is more interesting as if it is high it means you must have a good CI CD pipeline. I worked places where there were limits on commits a day due to monolith plus master CI/CD taking an hour. You then end up thinking of strategies like "I'll do that in the afternoon and get it to that state and it gets merged at this time" and so on. Which is inefficient.

Not every PR is a feature. There will be lots of laying groundwork. Stuff going in but not yet activated as a feature flag. Small changes often make roll back easier. Regressions easier to detect. You can blue green your little change and auto detect if it is causing latency or availability issues on 1% then 10% etc. of traffic. This means you can early detect and do easy roll backs as nothing much has changed.

Downside: your code is always a Frankenstein monster of feature flags that need to be cleared up! But hey that's more PRs to boast about.

Yeah I get itchy if the pipeline to prod ain't working for more than 24h for one microservice. I love continuous deployment.