To save on costs, QAs could be paid in exposure.

As an experiment / as a bit of a gag, I tried using Claude 3.7 Sonnet with Cline to write some simple cryptography code in Rust - use ECDHE to establish an ephemeral symmetric key, and then use AES256-GCM (with a counter in the nonce) to encrypt packets from client->server and server->client, using off-the-shelf RustCrypto libraries.

It got the interface right, but it got some details really wrong:

• It stored way more information than it needed in the structure tracking state, some of it very sensitive.
• It repeatedly converted back and forth between byte arrays and the proper types unnecessarily - reducing type safety and making things slower.
• Instead of using type safe enums it defined integer constants for no good reason.
• It logged information about failures as variable length strings, creating a possible timing side channel attack.
• Despite having a 96 bit nonce to work with (-1 bit to identify client->server and server->client), it used a 32 bit integer to represent the sequence number.
• And it “helpfully” used wrapping_add to increment the 32 sequence number! For those who don’t know much Rust and/or much cryptography: the golden rule of using ciphers like GCM is that you must never ever re-use the same nonce for the same key (otherwise you leak the XOR of the two messages). wrapping_add explicitly means when you get up to the maximum number (and remember, it’s only 32 bits, so there’s only about 4.3 billion numbers) it silently wraps back to 0. The secure implementation would be to explicitly fail if you go past the maximum size for the integer before attempting to encrypt / decrypt - and the smart choice would be to use at least 64 bits.
• It also rolled its own bespoke hash-based key extension function instead of using HKDF (which was available right there in the library, and callable with far less code than it generated).

To be fair, I didn’t really expect it to work well. Some kind of security auditor agent that does a pass over all the output might be able to find some of the issues, and pass it back to another agent to correct - which could make vibe coding more secure (to be proven).

But right now, I’d not put “vibe coded” output into production without someone going over it manually with a fine-toothed comb looking for security and stability issues.

Years of carefully curated anti-intellectualism in every bit of media they consume, because facts didn’t suit the wealthy (smoking is bad for you, fossil fuels are destroying the planet, private prisons drive more recidivism are facts that get in the way of someone making lots of money). Those fighting facts that aren’t on their side have embraced a number of other groups with anti-intellectual elements (white supremecists / neo-nazis / anti-woke, religious, anti-vaxxers, natural health advocates) to create alliances of anti-intellectual thought.

This has driven increasing polarisation in the US; 49% of republicans approved of JFK as president, and 49% of democrats approved of Eisenhower. It went down over time - other party approval was 30% of Carter, 31% of Reagan. There was a break in the pattern (44% for Bush Senior), but back on track to 27% for Clinton, 23% for Bush, 13% for Obama, 7% for Trump (first round), and 6% for Biden. So in other words, Americans are so polarised that they’ll vote for whoever their side puts up, and for one side, being anti-intellectual is actually seen as a strength.

I think many of the people who started the anti-intellectualism ball rolling on purpose are wealthy neoliberals who believe in laissez-faire free trade as a fundamental value, and so there is a certain aspect of ‘leopards ate my face’ to this leading to the anti-intellectualism extending back to rejection of mainstream economics (even though the neoliberals’ preferred theory is notoriously flawed, Trump’s approach to pulling economic levers is wholesale rejection of all theory rather than replacing it with something less flawed).