I hear you. I suppose I have never been in a situation where I continued using the same debug code for months in a row, usually something is broken, I diagnose writing appropriate tools, fix it and move on. The next time the situation is different, so I always adapted any previous tooling.
Thank you for the kind appreciation and supporting me limiting the scope to what I know, Dipankar.
I'm not sure, In my book I share practices that work for me, I have never had a "dull" tool in my debugging practice thus it's not there.
I'm new to using AI so I don't yet have enough experience to answer your question.
Until now all the debugging I did was done manually so nothing was aged or silently dropped, haven't had this problem.
I imagine that with time there will be new sections covering AI-use specifics, but I need to gain more experience first.
At the moment it's a an exact-match, later will support partial match as well.
Thank you for the kind words, Dipankar
The lion share of speed up comes from prompt deduplication during generation and training.
I pinged Elio to see if he wants to join.
Thank you for the kind words, Jeff!
We are still waiting for BLOOM v2.0 from HF!
