mfjordvald

>Your job is to design, the AI builds like the junior engineers. Then you review their work.

I'll add to this that your job is also to design tooling and feedback loops that allows the AI to improve over time.

You have policy gates: How the AI should act. (and a feedback loop to check the code is adhering to those policy gates)

You have quality gates: How the AI verifies it's done things correctly (testing, linting, PRDs, cyclomatic complexity)

Modern AI engineering is really about improving this system rather than manually reviewing AI output. The better the policy gate and quality gate enforcement, the less manual review is required and the more velocity you achieve.

Sticking with being a human-in-the-loop reviewer of AI code is where people lose all hope in still being software engineers.

There's tons of options, no-intro, redump, tosec, mame are all doing DAT files with file checksums.

That said, ROMs are basically never a malware vector as they have to exploit an issue in the emulators themselves and historically that hasn't really been seen. Typically malware related to roms happens with files included in the zip archives or by sites offering "downloaders" with embedded malware.

This argument kind of falls apart when you consider Europe has virtually free education and some parts like Scandinavia pay a sizeable stipend to students of higher education.

It might be a contributing factor in some countries, but there's definitely more going on.

Egg temperature plays a definitive role in the sex of turtles, but no one would claim it in the realm of possibility for that to affect humans.

It's always good to be aware of how things affect human hormones and absolutely worth study and regulation, but it's a huge jump from frogs are affected to humans are affected. I know right wing people are world class long jumpers so this kind of "it could be!" really isn't helping towards a reasonable debate.

Side note, but the small font size + light grey text on the white background made it a bit of an eye strain for me to read your story, would definitely benefit a bit from some more contrast.

Google news app insists on opening in a chrome-based webview without ad blocking. Large part of why I rooted to get adaway.

I feel like you're personally attacking me haha.

I don't really need it for getting jobs but I definitely moved on to other topics and just never kept up with the blogging.

Most NFTs are still made on the Ethereum mainnet which has huge gas fees indeed. There are alternative protocols which make it cheaper but it's a pain (and expensive) to move over to those protocols.

There are some projects working on reducing this though, for example zkSync is doing some really interesting work on a layer2 solution that feels like you're staying on the Ethereum mainnet but the fees are highly reduced thanks to the zkRollup algorithm.

I saw my friend mint an NFT for $1.40 the other day just to showcase the work zkSync has been doing, at this cost it'd be super interesting for real world uses beyond just art provenance.

They have been for decades! Most scene releases that are packed will include an SFV file that contains the checksums of each of the package files so that you can check the file integrity.

Obviously those can be repacked and faked so you'd have to check multiple sources to ensure you get a genuine release, but yeah the scene groups are as usual way ahead of everyone else.

Netherlands though, not the US. If they're anything like most of Europe then a doctors note is all you need to still be paid while sick more than 1-2 days.

To be fair, there's a world of difference between a single POP HE connection and the globally distributed AWS CDN. Understand your use-case and what factors are important because HE has significant drawbacks in some cases.

Don't think so, from what I understand, the problem was the intermediate certificate expired, it would have expired regardless if there were no automatic updates.

> While we were building the model we also wanted to figure out what to do for these Pinners once we could target them. We thought it would be best to ask them, as they surely would know why they were using Pinterest less. So we did an in-product survey for a sample set, and found the most common reason for not using Pinterest was that they got busy.

They did mention contacting users and, as is usual, got only the symptom, not the underlying cause. Talking to users is great to understand why something happens is great, but it has to be translated through deep product insight to be useful.