12 comments

  • lewtun 13 hours ago

    Hi, Lewis here (one of the co-authors). Happy to answer any questions people have about the book :)

    • danielmarkbruce 12 hours ago

      I'm a little ways through this and it's great so far, nice job.

      One of the reasons people build one though is to learn. Most smart folks are quite aware that the reality of pre-training a real LLM is going to involve some head banging against the wall (ie, things don't go smoothly like "building an llm from scratch" book), and they want to go through the process.

  • tsenturk 21 hours ago

    Hugging Face is not just an AI information-sharing website; it’s also a great learning platform for all AI learners. This documentation is one of the most impressive hands-on resources I’ve ever read.

    • abossy 15 hours ago

      What others would you recommend that are comparable in quality?

      • pixelmelt 12 hours ago

        Been reading a book by u/fpham "The Cranky mans guide to lora and qlora" and it's pretty great, writing quality isnt all there but the content is valuable for learning to make good finetunes

      • donkeyboy 14 hours ago

        The documentation for common ai packages is pretty good too. For example, pytorch docs, peft docs, timm docs.

  • forgingahead 7 hours ago

    Where does "Smol" come from? It's supposed to mean "Small" right? If yes then what's the etymology and reason for popular usage?

  • doctorpangloss 6 hours ago

    I really like the Hugging Face guys, but...

    > Modify one thing at a time

    > Change only one variable per ablation while keeping everything else constant. If you change multiple things and performance improves, you won’t know what caused it. Test modifications individually, then combine successful ones and reassess.

    This is an unintentional microcosm of what is flawed with the document.

    • CamperBob2 6 hours ago

      What's wrong with it? That's good advice in almost any optimization or troubleshooting context where variables may interact.

      • yorwba 3 hours ago

        One problem with testing one change at a time is that if you can only run a small number of experiments because each one requires many GPU hours to get results, you can also only test a small number of changes. If you can come up with and implement new changes much more easily than you can test them, it would be more efficient to test multiple changes at a time and use some form of Bayesian optimization to find the best combination of changes with as few experiments as possible.