wy1981

The author seems to have published math papers (as one can see on DBLP and other websites) and a PhD in maths. It gives me confidence that it's written by a human and also reading chapter 1 and chapter 2 I think there is a human behind it, not an LLM.

Questions for folks familiar with fine-tuning: what are the best resources to learn fine tuning?

I could have overlooked but doesn't seem there is a mention of Claude in the blog post? Did author say they had used Claude?

I also am wondering if Claude will proceed on a prompt which is about finding a bug like that? I am not sure, has anyone tried?

There is a Pakistani variant called "Anwar Ratol" which is not in the list. I believe, it's the best mango variety ever.

Can someone please recommend a good English version of "De Newton a Einstein y algo más eBook" (the book mentioned in the blog post) or a similar book?

Jeff Dean, Sanjay, et al have achieved so much. I'm very happy for them. Truly deserving.

Sometimes I couldn't resist wondering if I'll ever do work that has a tenth of the impact of theirs.

Thanks for responding.

If you're interested in a tutoring Latin remotely, please let me know. If not, no worries.

As an aside, do you still teach Latin? If not, any online recommendations for Latin tutors? Thanks in advance.

This level of detail isn't really helpful. I am working with AI and genuinely interested in learning more, but this offers very little.

More concrete examples to illustrate the core points would have been helpful. As-is the article doesn't offer much - sorry.

For one, I am not sure what kind of code he writes? How does he write tests? Are these unit tests, property-based tests? How does he quantify success? Leaves a lot to be desired.

What works for me is that often on a Monday I restart my machine. If something is truly important, I save it before the restart. There is something good to start from an empty state.

> Every project and programmer shouldn't feel they have to justify their choice not to use Rust

Maybe writing about it was taken as an opportunity to clarify their own thinking about the topic?

Looks nice. Some explanation for those of us not familiar with Go would've been more educational. Could be future posts, I suppose.

Great find and writeup.

As an aside, this is the type of a problem that I think model checkers can't help with. You can write perfect and complicated TLA+/Lean/FizzBee models and even if somehow these models can generate code for you from your correct models you can still run into bugs like these due to platform/compiler/language issues. But, thankfully, such bugs are rare.