I don’t see how I would feel comfortable pushing the current output of LLMs into high-stakes production (think SLAs, SRE).

Understanding of the code in these situation is more important than the code/feature existing.

You can use an agent while still understanding the code it generates in detail. In high stakes areas, I go through it line by line and symbol by symbol. And I rarely accept the first attempt. It’s not very different from continually refining your own code until it meets the bar for robustness.

Agents make mistakes which need to be corrected, but they also point out edge cases you haven’t thought of.

Definitely agreed, that is what I do as well. At that point you have good understanding of that code, which is in contrast to what the post I responded suggests.

I agree and am the same. Using them to enhance my knowledge and as well as autocomplete on steroids is the sweet spot. Much easier to review code if im “writing” it line by line.

I think the reality is a lot of code out there doesn’t need to be good, so many people benefit from agents etc.

And DEF is ~33% urea in water.

I've done that in the past (8+ years ago) with raw IP sockets.

For 8+ bays you just need a SAS HBA card and one free PCI-E slot. Not to mention that many motherboards will have 6+ SATA ports already.

If anything, 2nd hand AMD gaming rigs make more sense than old servers. I say that as someone with always off r720xd at home due to noise and heat. It was fun when I bought it during winter years ago, until summer came.

I've been turning off my home server even though it's a modern PC rather than old server hardware because it idles at 100W which is too much. Put a Ryzen 7900X in it.

Not sure if it's not properly doing lower power states, or if it's the 10 HDDs spinning. Or even the GPU. But also don't really have anything important running on it that I can't just turn it off.

> For 8+ bays you just need a SAS HBA card and one free PCI-E slot. Not to mention that many motherboards will have 6+ SATA ports already.

And what case are you putting them into? What if you want it rack mounted? What about >1gig networking? What if I want a GPU in there to do whisper for home assistant?

Used gaming rigs are great. But used servers also still have loads of value, too. Compute just isn't one of them.

> And what case are you putting them into?

Maybe one of the Fractal Designs cases with a bunch of drive bays?

> What if you want it rack mounted?

Companies like Rosewill sell ATX cases that can scratch that itch.

> What about >1gig networking?

What about PCI Express card? Regular ATX computers are expandable.

> What if I want a GPU in there to do whisper for home assistant?

I mean... We started with a gaming rig, right? Isn't a GPU already implicit?

> Companies like Rosewill sell ATX cases that can scratch that itch.

Have you looked at what they cost? Those cases alone cost as much as a used server. Which comes with a case.

> What about PCI Express card? Regular ATX computers are expandable.

As mentioned higher up, they run out of lane count in a hurry. Especially when you're using things like used Connect-X cards

A rackmount case from Rosewill costs a couple of hundred bucks or so, new. And they'll remain useful for as long as things like ATX boards and 3.5" hard drives are useful.

I mean: An ATX case can be paid for once, and then be used for decades. (I'm writing this using a modern desktop computer with an ATX case that I bought in 2008.)

PCI Express lanes can be multiplied. There should frankly be more of this going on than there is, but it's still a thing that can be done.

Consumer boards built on the AMD X670E chipset, for instance, have some switching magic built in. There's enough direct CPU-connected lanes for an x16 GPU and a couple of x4 NVMe drives, and the NIC(s) and/or HBA(s) can go downstream of the chipset.

(Yeah, sure: It's limited to an aggregate 64 Gbps at the tail end, but that's not a problem for the things I do at home where my sights are set on 10Gbps networking and an HBA with a bunch of spinny disks. Your needs may differ.)

Traditional CMOS D-flipflop takes 16 transistors, SRAM cell takes 6 (two looped inverters and two data-line selection transistors).

The capacitor in DRAM is usually realised as an enlarged gate of a transistor AFAIK.

It is always PWM under the hood, the question is, how much was spent (or not) on the filtering network out of the PWM. Is it closer to buck converter or is it straight up flicker at the output.

Since these things have lots of LEDs, my first thought was to put a range of different tiny delays on them to induce destructive interference, so that the off parts of one LED's flicker are the on parts of another, to smooth out the overall output.

Actually that's not true, my first thought was "just use a layer of phosphor excited by the LEDs", but fluorescent tubes do that and people used to make the same complaints about flicker, so.

Looks like "flicker index" is a useful(?) search term, anyway.

Nobody runs 4096 samples per pixel. In many cases 100-200 (or even less with denoising) are enough. You might run up to low-1000 if you want to resolve caustics.

IIRC reordering additions can cause the result to change which makes auto-vectorisation tricky.

You can think of closing the channel as sending a message “there will be no further messages”, the panic on write is enforcement of that contract.

Additionally the safe way to use closing of a channel is the writer closing it. If you have multiple writers, you have to either synchronise them, or don’t close the channel.

Sure but the fact that it is shared state is why you can't naively have a go channel that spans a cluster but Erlang's "actor" system works just fine over a network and the safety systems (nodedowns, monitors etc) are a simple layer on top.

Majority of good spots for hydro were already built up, and if they weren’t, good luck with NIMBY.

meant of the good spots are already used, but we can change how they are used to greatly increase their usefulness to a 0 carbon grid. we can make them all pumped hydro, and start treating hydro as a battery rather than a generation source.