fsddfsdfssdf

7 ms·

1.
by fsddfsdfssdf 3mo ago
If you want real numbers start selling hard drugs. You don't have to "serve the people". YouTube is a cesspool.
2.
by fsddfsdfssdf 3mo ago
> As a professional YouTuber Well, there's your problem. You want the numbers that come from mass consumption, which means catering to the lowest common denominator thus producing shit with gold plating while then complain the gold
3.
by fsddfsdfssdf 3mo ago
Conversations in its training data that explicitly mentioned "make no mistakes" don't strike me as particularly rich sources of high-quality reasoning signals. They strike me as conversations with Pointy-haired Bosses.
4.
by fsddfsdfssdf 3mo ago
You jest but I indeed find rejection an integral part of the job. Not plainly saying "no, get away", but backing up, requesting big picture views and trying to see if the overall organization is in need of and capable of carrying
5.
by fsddfsdfssdf 3mo ago
> You still need to architect the system to encode the invariants in types. That's the problem though, right? If it's pointed out we all agree the "do not keep credentials alive" is a property that should hold and we
6.
by fsddfsdfssdf 3mo ago
Yes, I agree. I find the addition of the regression test the true long-term fix. The code is just an opaque incantation that may or may not preserve some property we find worth preserving and we have no way of knowing it keeps preserving it
7.
by fsddfsdfssdf 3mo ago
While I can see the shortcomings of C and generally don't recommend it for new projects I don't see this particular bug as a good example of something Rust's borrow checker or some other language's type system will catch
8.
by fsddfsdfssdf 3mo ago
Changing a few words is thus enough to clear this case. What's the point of this exercise exactly? Both products are so incredibly derivative and boring that I find it very, very hard to care about this "case".
9.
by fsddfsdfssdf 3mo ago
Well done, Claude!