Kriemhilt
Kriemhilt t1_iwg55em wrote
Reply to comment by dsjoint in Indoor climbing, Me/chedilkm, Digital, 2022 by chedilkm1
Kid clearly has mad open-hand grip strength!
Kriemhilt t1_iszzlcw wrote
Reply to comment by Awkward-Event-9452 in DeepMind AI One-Ups Mathematicians at a Calculation Crucial to Computing by Acceptable_Berry_393
This ML model, after the solution space was painstakingly characterized by humans, found matrix multiplication algorithms up to 20% faster than the naive one.
I don't think that this is a big step on the way to strong AI.
Kriemhilt t1_iseot45 wrote
Reply to comment by Joeclu in Drawing inspiration from nature, researchers developed a medical adhesives that stops blood loss and promotes blood coagulation. The adhesive can also be removed without causing re-bleeding or even left inside the body to be absorbed by giuliomagnifico
Sounds like the adhesive is a porous gel designed to let the liquid part of blood through while keeping the clotting agents and other solids in place. So, it ought to allow normal clotting behaviour in situations where blood loss would otherwise be too fast to allow clots to form. If the adhesive is removed after the clot has formed ... there's still a clot there.
Kriemhilt t1_iycsjrt wrote
Reply to comment by OldHellaGnarGnar2 in ELI5: why is using "goto" considered to be a bad practice in programming? by Dacadey
The normal term for "the burden of working with rubbish code that is hard to understand or change" is technical debt.
One of the advantages of calling it that is that it sounds sort-of like financial debt, so you're putting it in language management might find easier to understand. You ideally want some concrete motivation though, like
>"technical debt will make it slower (and therefore more expensive) to add these features you want, but if we invest in reducing our technical debt first, those features will arrive sooner and have fewer bugs."
If they don't have any bugs to fix or features to add, this obviously doesn't help you much!