forgotmypw17

>It's sort of weird in a world that has moved to an DevOps-style ethos for most development.

The world at large makes all sorts of trends, and that by itself doesn't make them smart. As a developer, you are likely to have blind spots when it comes to quality and reliability as a result of having written the code. Even a team of developers cross-testing each other's code will not have the same ability to find flaws (before they embarrass you in front of the customer/client/user) as a dedicated tester whose job it is solely to find new (and old) ways to break things (and document them.)

DevOps is a completely different thing (though they work together with testers.)

It is only weird to have dedicated QA on your team if you don't give a fuck about releasing shit with bugs in it for the user to bump into.

Any

Working pretty well for me.

Ah, I noticed this yesterday, figured it was just me.

While we're here, does anyone know a screen recording application that automatically takes into account display changes, audio device changes, camera resets, etc.?

I'm making do with OBS, but I lose more video to "plugged in external monitor and forgot to update OBS config" than I actually record.

Must be the first thing I've ever read on lesswrong in its entirety, let alone in one sitting.

Most similar thing I can think of is "The Metamorphosis of Prime Intellect". Metamorphosis of Prime Intellect is way better and more comprehensive, imo.

Agree, we use OpenPGP.js in our web projects. It's great for combining it with server-side GnuPG.

It used to be more of a concern without TLS, but now it's reasonably secure to use.

We use it for the user sessions, allowing the client to own their session and identity.

The browser generates the keypair and signs each post and login challenge, so the private key never leaves the client. The server only stores the public key (as a plaintext file in git) and verifies signatures with GnuPG, which means there's no password hash in the database to leak, and the identity is just a fingerprint anyone can audit. Using two independent implementations (OpenPGP.js on the client, GnuPG on the server) is a nice bonus.

I have preferred not using a framework for a while, pre-LLM, because frameworks would introduce many new failure modes into my codebase, including: - bloat and assumptions I didn't ask for - constraints that I otherwise wouldn't encounter - failure modes related to the framework making breaking changes in updates

However, this basically meant implementing my own framework in a project. Which was fine.

I have now, over time, constructed a framework for agentic coding, because I found myself using the same prompting patterns...

OkCupid did it back in the day...

Would you feel the same thing about "the need to mention it specifically" if they had mentioned their boyfriend?

Your phrasing reminded me of what casual mentions of a same-sex partners used to elicit, when heteronormativity was more prevalent.