A common argument for choosing to use rust is: "Well, it's memory safe isn't it?". But that is not a good argument; many (most) languages are memory safe. "But it gives you speed/concurrency and control?", yes but so does C, C+
Imagine you're me - struggling to debug unstable training[1] - then while taking a detour[2] into optimizers you find out that not only does batch accumulation affect the step-size (effective learning-rate), the scalar loss value you end up with also scales the gradients. I had assumed
In the process I made a disk image of my OS, in case I needed some data I forgot to back up. Now I could have restored the disk image, booted into it, and then back it up. But then I got an idea, what if I just boot into it with QEMU.
It's a framework based on a paper by OpenAI, however at this point we have far increased the functionality described in the paper. We also have a roadmap for other features which are planned to be implemented, such as ESAC.
A small research created on how Invoice Manager is usable for reoccurring billing situations aka subscriptions. Here I explain how it currently is done, what an optimal solution would be and a proposed solution sketch. With subscriptions, I am referring to the reoccurring invoices for our contacts. E.g: hosting,