klysm

34 ms·

631.
by klysm 2y ago
Indeed plans get hard when the plan has to be dynamic. Pulumi and terraform have similar troubles.
632.
by klysm 2y ago
> It is hard to scale when there just aren't the incoming materials yet. There are a huge number of businesses already doing this today - there is plenty of incoming materials from just old cars alone. The amount of aluminum in this
633.
by klysm 2y ago
Yes they are very limited. The sum of two uniform distributions is not uniform. If you care about the probability density within the interval you need to reach for more advanced methods.
634.
by klysm 2y ago
Is this equivalent to open intervals e.g. (0, null)?
635.
by klysm 2y ago
A good mental tool for thinking about that is adding two dice rolls
636.
by klysm 2y ago
Gaussian distributions are a horrible choice for representing measurement uncertainty. If the tool is properly calibrated, 100% of the probability mass will be within (6.9, 7.1). A normal distribution would have probability mass in negative
637.
by klysm 2y ago
I'm not sure why you are being downvoted - this is absolutely true.
638.
by klysm 2y ago
I would consider this a massive success!
639.
by klysm 2y ago
Metal recycling is critical for both the metal resources themselves and the carbon reduction. Secondary aluminum production is much less carbon intense than primary. New sorting technologies have been developed which enable fine separation
640.
by klysm 2y ago
Sometimes it’s useful if the mean/median has meaning
641.
by klysm 2y ago
Shoving your head in the sand instead of learning from mistakes doesn’t seem very productive
642.
by klysm 2y ago
Set a short timeout on lock acquisition, eventually it will get through or you have to tolerate a larger timeout
643.
by klysm 2y ago
Interesting idea. This makes intuitive sense to me but I’ve never seen code written like this or attempted to write code like that. I’ll have to try it out next time I’m using numpy.
644.
by klysm 2y ago
The intersection into epistemology is very interesting
645.
by klysm 2y ago
This is definitely part of the future for better storage systems. Too much responsibility is currently in the hands of programmers (like me) to not make any mistakes. The storage layer can be a high consequence place to make a mistake!
646.
by klysm 2y ago
It would be way better to use a binary representation of the structure
647.
by klysm 2y ago
I’m not confusing latency and bandwidth. Serialization does contribute to latency everywhere, you have to wait for the decoder or encoder. It’s another step
648.
by klysm 2y ago
things like this happen all the time when we didn’t implement name spacing when we should have
649.
by klysm 2y ago
A violin plot is literally just a KDE sideways.
650.
by klysm 2y ago
100% on the money. Box plots are an archaic technique for working around limitations that no longer exist.
651.
by klysm 2y ago
I think there is an aversion to just showing the damn distribution as a histogram or KDE. I hear arguments from product owners that it’s “too complex” etc.
652.
by klysm 2y ago
Memory is a weird thing.
653.
by klysm 2y ago
Huh I thought go was supposed to make concurrency easier. That seems very tricky to get right
654.
by klysm 2y ago
Changing money to decimal seems like a mistake - it must’ve been money in the first place for a reason
655.
by klysm 2y ago
No amount of automation has ever seemed to result in a net reduction in work to do thus far
656.
by klysm 2y ago
Cherry-picking is harder. Splitting up the branch is harder.
657.
by klysm 2y ago
Can’t use the battery if the device is shattered. No case is not an option for my clumsy self. Turning off my phone at night is not an option. I want to be contactable in case of emergencies.
658.
by klysm 2y ago
I agree you can do whatever you want on your private branch. Unfortunately I think a lot of developers don’t have a solid grasp of what’s possible in private, and more importantly what you should do in private vs. on public branches.
659.
by klysm 2y ago
The problem I run into is when a developer merges the main line branch into their feature branch repeatedly to get new changes. Now your branch is completely tangled up and difficult to change
660.
by klysm 2y ago
Always use --force-with-lease.

More ›