You're interested in the different between a single CPU and 8 GPUs? A Ford fiesta vs a freight train.
One can be interested in the differences between a Ford Fiesta and a freight train…
Readit Newsmrnonchalant commented on Serving AI from the Basement – 192GB of VRAM Setup ahmadosman.com/blog/servi... · Posted by u/XMasterrrr
Very cool! I liked the instruction counting article as well.
https://blazeti.me/
I don’t know what it means, but it’s provocative.
mrnonchalant commented on Robot Learns to See in 30 Minutes (2022) antonilo.github.io/vision... · Posted by u/stoniejohnson
Looking forward to seeing the code! Any sense how soon “soon” might be?
mrnonchalant commented on Overhead of Python asyncio tasks textual.textualize.io/blo... · Posted by u/willm
async tasks are cool, but the usual PSA applies here:
Be careful to hold your references, because async tasks without active references will be garbage collected. I've been bitten by that in the past.
Long discussion here: https://bugs.python.org/issue21163
Docs: https://docs.python.org/3/library/asyncio-task.html#asyncio....
"Important
Save a reference to the result of this function, to avoid a task disappearing mid-execution. The event loop only keeps weak references to tasks. A task that isn’t referenced elsewhere may get garbage collected at any time, even before it’s done."
Thanks for this!
CS departments come in two flavours: systems and theory. The more dogmatic of each both eschew recursion, but have motivations that are diametrically opposed. :)
What are the reasons?
mrnonchalant commented on An unexpected benefit of unit tests matthewc.dev/musings/unit... · Posted by u/matthewfcarlson
I was going to say the same thing. His characterization of TDD as "writing a whole smattering of tests and then coding until they all pass" suggests he's gotten some bad information about TDD. Sadly common, though.
His TLD is pretty much TDD except he doesn't mention refactoring after passing the tests. Even leaving a failing test at the end of the day as a kind of "todo" for the next day, I'm pretty sure Beck mentioned using that idea in his TDD book.
EDIT: Found it finally. From Beck's Test-Driven Development by Example (page unknown, ebook copy, chapter 27):
> How do you leave a programming session when you're programming alone? Leave the last test broken.
> Richard Gabriel taught me the trick of finishing a writing session in midsentence. When you sit back down, you look at the half-sentence and you have to figure out what you were thinking when you wrote it. Once you have the thought thread back, you finish the sentence and continue. Without the urge to finish the sentence, you can spend many minutes first sniffing around for what to work on next, then trying to remember your mental state, then finally getting back to typing.
> I tried the analogous technique for my solo projects, and I really like the effect. Finish a solo session by writing a test case and running it to be sure it doesn't pass. When you come back to the code, you then have an obvious place to start. You have an obvious, concrete bookmark to help you remember what you were thinking; and making that test work should be quick work, so you'll quickly get your feet back on that victory road.
> I thought it would bother me to have a test broken overnight. It doesn't, I think because I know that the program isn't finished. A broken test doesn't make the program any less finished, it just makes the status of the program manifest. The ability to pick up a thread of development quickly after weeks of hiatus is worth that little twinge of walking away from a red bar.
I like this a lot actually l
mrnonchalant commented on What should I do Before I give up programming? · Posted by u/shivajikobardan
Keep suffering upward!