bblcla

Thanks!

One thing I've found while working in the ML space is that it seems like ML researchers have to deal with a lot of systems cruft. I think that in the limit, ML researchers basically only care having about a few things set up well:

- secrets and environment management

- making sure their dependencies are installed

- efficient access to their data

- quick access to their code

- using expensive compute efficiently

But to get all this set up for their research they need to wade through a ton of documentation about git, bash, docker containers, mountpoints, availability zones, cluster management and other low-level systems topics.

I think there's space for something like Replit or Vercel for ML researchers, and Moonglow is a (very early!) attempt at creating something like it.

Good question! I'm not too familiar with Zed, but here's my high-level guess from reading the website: we don't currently integrate with Zed, but we probably could if it supports remote kernels (the docs I found at https://zed.dev/docs/repl weren't specific about it).

One nice thing about our VSCode extension is that it's not just a remote kernel - our extension also lets you see what kernels you have and other details, so we'd need to write something like it for Zed. We probably wouldn't do this unless there's a lot of demand.

By the way, VSCode also supports the # %% repl spec and Moonglow does work with that (though we haven't optimized for it as much as we've optimized for the notebooks).

We don't right now, but it's something a lot of people have asked for, so we're rolling out a file sync feature next week. (It will basically be a nice wrapper over rsync.)

I have also heard that failure rates on new GPUs are very high (approaching 20% if not burnt in), so that's unsurprising.

It's the other stuff I was more surprised about. I would have guessed that having your Ethernet cables plugged in and power supplies tested was table stakes nowadays. Then again, I've never been a datacenter admin...

This part in particular caught my eye:

> Step 2: Diagnosing broken machines

> As is typical in setting up large GPU clusters, we found that about 10% of the machines failed to boot, mostly due to physical issues with the servers. Some issues we encountered included: unconnected or miswired Ethernet cables, hardware issues in iDRAC, broken power supply units, bad NVME (nonvolatile memory express) drives, missing internal wires, and network cards or GPUs failing to show up.

This is a crazy high failure rate. Is this standard for traditional data centers too?

Friends don't let friends become Vietnamese billionaires!

Honestly, I didn't realize until I was 2 or 3 years into my job that I was 'allowed' to take a sick day if I was going to spend it all miserable or even crying (I had a coworker who was a bully).

Nobody ever actually came out and so, but I realize now that it was pretty common.

This is cool! Wish it was available for more cities, though.

Yes. I tried to get car insurance in July in California and barely succeeded — I had to walk in to an AAA branch and they quoted me 2-3 times the Geico price.

Geico will quote a price but forces a 15 days waiting period. Then they’ll send you snail mail and ask you to send in a picture of your car within two days, by snail mail. This is the car you don’t have insurance on, so it’s probably still at the dealer’s or at the seller’s house! I think they’re not allowed to actually refuse to sell insurance but they’ll do everything they can to make it annoying enough that you go away. State Farm and the others are all equally bad.