@thomasfuchs andreessen was a lucky bugger while being an idiot. He remains an idiot,
Notices by noplasticshower (noplasticshower@zirk.us)
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Tuesday, 16-Jul-2024 23:35:17 JST noplasticshower
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Friday, 12-Jul-2024 05:09:08 JST noplasticshower
@georgetakei let it fill you with resolve NOT FEAR
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Thursday, 30-May-2024 05:30:48 JST noplasticshower
@uspolitics Republicans can't govern
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Friday, 09-Feb-2024 18:18:29 JST noplasticshower
@ElleGray terrorist trash panda
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Sunday, 21-Jan-2024 08:03:35 JST noplasticshower
@rysiek you're missing stochasticism
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Sunday, 21-Jan-2024 08:03:33 JST noplasticshower
@rysiek in fact, it makes it significantly worse
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Sunday, 21-Jan-2024 08:03:31 JST noplasticshower
@rysiek sure. Usual testing assumes determinism. When we run a test we get the same wrong answer until a bug is fixed. With stochastic code, the "right" answer is much harder to define. It is much easier in that case for wrongness to slip by. And it's really hard to get stochastic code into the very same state to find a bug (or watch it) twice. Believe me, my thesis code was non-deterministic and it was a pain in the ass to debug.
-
Embed this notice
noplasticshower (noplasticshower@zirk.us)'s status on Sunday, 21-Jan-2024 08:03:30 JST noplasticshower
@rysiek Remember, we use ML (or should only use it) when we can't explicitly code HOW so we instead pile up the WHAT and make a machine become that.