I see, thanks for the info! I'm still new in all of this stuff and sometimes I don't know if some errors happen because of (my) bad programming skills or because de web is down hahaha
"It was remarkable to see how many errors could be stuffed into 5 minutes of vacuous conversation." open.substack.com/pub/programm...
Malkovich. Malkovich. Malkovich?
"It was remarkable to see how many errors could be stuffed into 5 minutes of vacuous conversation ... the errors systematically pointed in a particular direction. In every instance, the model took an argument that was at least notionally surprising, and yanked it hard in the direction of banality.""It was remarkable to see how many errors could be stuffed into 5 minutes of vacuous conversation ... the errors systematically pointed in a particular direction. In every instance, the model took an argument that was at least notionally surprising, and yanked it hard in the direction of banality."
Malkovich. Malkovich. Malkovich?
One way I fight this tendency is to have explicit written expectations for different levels in the lab. For example, for an undergrad with sufficient in-lab training, I expect them to keep a clear notebook and perform routine tasks without errors. Anything more is gravy. 3/🧵
errors to
realized i made a few spelling/grammatical errors only after posting, whoops
okay that's an argument against capitalism, not automation make an argument against automation, when it leads to less errors, increased worker safety, greater accountability, lower costs over time.
something about how intensely loveable nature of David Mitchell combined with the strange unforced time-period-errors and the odd flatness of the individual murder stories but the deep emotion about the missing dad together say... how about if you looked in a mirror and saw Bob from Twin Peaks?
The guy writing National Weather Service bots for bsky mentioned getting lots of weird rate limit errors for no reason, I know that much.
Coding all day long, Bugs and errors never end, Coffee is my friend.