SmooL

I've been having a good time with Spec Driven Development, and it directly addresses the issue of needing the understand.

The whole idea is that you specify exactly what you want in some SPEC.md file. You can of course nest them, have multiple, etc, but the core idea is that the SPEC file is the source of truth, and all the code should be able to be generated by a competent agent into the working product you want. The SPEC file(s) should contain all the details and behavior you care about, and anything you don't care about is up to the agent to decide. If you don't like what the agent picked, _put it in the spec file_.

Critically, _you_ must write the SPEC file. You ensure understanding by doing so. You can of course ideate with the agent, but it's your ideas, in your words, specified by you. This also makes it a great source of documentation when you come back later and have to remember wtf is going on in this codebase.

I can trivially just print any AI image I want, then take a "verified" picture of it with my camera. That seems like a pretty large failure point.

The thinking goes: - any job that can be done on a computer is immediately outsourced to AI, since the AI is smarter and cheaper than humans - humanoid robots are built that are cheap to produce, using tech advances that the AI discovered - any job that can be done by a human is immediately outsourced to a robot, since the robot is better/faster/stronger/cheaper than humans

That OpenAI demo is available right now to subscribers; I have access to it

Ironically, it seems the article itself was written by AI

There's no good reason for BTC to be set up to use that much energy. There are viable, proven alternatives like proof of stake. I'd also be more forgiving if BTC only required a given amount of power, but no, the system is designed such the power requirement is related to the cost of flops/watt - it's specifically designed such that the system will use more power as power becomes cheaper.

Isn't that a bit of a cop-out though? They're just redefining the word "intelligence" to be something else (here, the ability to learn new things). That's fine and all, but that doesn't answer the question we actually care about, which is the absolute magnitude of the ability. It doesn't matter how "long" an entity took to learn, or how "efficient" they were in learning - at the end of the day, AlphaZero will crush Magnus.

It was a multi year effort mainly around 2015/16 but extended into 2018 IIRC

Genuine question: are the health risks really that bad? Plastic has been around for decades - surely also then these micro/nano plastics have been around for decades? I can't help but feel like if there were obvious and large health effects that we'd have noticed by now.

This is either brilliantly absurd, or ridiculously stupid, depending on your POV

This is not a fair comparison - Tesla is comparing miles driven by their systems, which are inherently limited in scope to "easier" scenarios (only lane assist/only on highways/ect), against total US average, which includes _all_ gnarly road situations.

Yes, but transmission lines can only go so far, and you still lack the ability to arbitrage over time instead of just spatially. E.g. from a solar power POV, it's night everywhere in a given region at the same time.

> My gut feeling is that transmission lines would still be cheaper

Transmission lines are great for moving electricity, but only if there's demand for that electricity _right now_. Otherwise, you have to store it - which is a problem, because battery tech right now isn't great (or rather, it's not good enough for grid-scale requirements) . This iron powder could be thought of as a "battery". It might be harder to move than compared to a transmission line, but it's _stored_ energy and can be redeemed at a later time.

1. It's opinionated, so there's often only one way of doings things. Largely, the "one way" is a good way, so people appreciate the forced consistency 2. It's simple. It is very easy to read and write. It is hard to shoot yourself in the foot. 3. It's powerful. They have a few core abstractions that compose well (generic io, http stuff). 4. It's fast. It runs fast because it's compiled, and it compiles fast because it's simple.

Me personally: I appreciate the simplicity of it. It's a great language for working with in a team. I wish it was more functional, and had better ways to handle errors, but the simplicity of it all was a breath of fresh air using it in a working environment.