amethyst

We were benefiting from stacked pull requests in Phabricator for a decade before "AI" was a thing. Having well scoped commits that can be individually actioned by distinct sets of reviewers has always been extremely useful.

We did these sorts of exercises in my high school social studies class, in Ohio, back in 2002ish. I fear it may have been instructive to some of my classmates rather than warning them of the inherent evils.

  Location: California
  Remote: Yes
  Willing to relocate: no
  Technologies: Python, Rust, SQL, fullstack
  Résumé/CV: https://amethyst.cat/resume
  Email: [email protected]

Senior engineer with 13 years in FAANG and plenty of experience working on core Python developer tooling, build infrastructure, and backend services. Most recently at Astral working on Ruff. Looking to bring my broad expertise to any company with a human-focused mission that won't require me to use AI agents to get my work done.

3) recipient stores decrypted content in plain text and backs that up in well-known cloud storage systems

Is it really holding them "accountable" when the settlements are for laughably small amounts, like <1% of a single day's profit?

If it's anything like Facebook, the side entrances (which always had guards sitting by them anyways) were all converted to alarmed fire exits. So the fire marshal would still be happy, but it was far less convenient for employees.

It works pretty well for Apple

tools like dataclasses and pydantic would like to have a word...

Google Fiber isn't rolled out to most of the bay area. Monkeybrains is wireless with speeds significantly slower than what Comcast offers me. I've checked just about every wired ISP possible, and Comcast is the only option that services my neighborhood.

And FWIW, I own my house in the east bay — I am the landlady ;)

*parts of the Bay Area. I'd say the majority of areas are still monopolized by Comcast, including my neighborhood of course.

In markets where Comcast has actual real competition, they "include" the unlimited data (aka no cap) with no extra charge when you sign up for their gigabit plans.

And yet it's the default when formatting a device on macOS.

And yet, as someone working on core language infra, we apply exactly that sort of ideal when making changes. If a diff doesn't break any tests, then it's "safe" to land, and if something does indeed break afterwards, then it's the broken team's responsibility to fix forward or otherwise provide proof that it's a big enough problem to roll back. If we end up in SEV review for a change, and there were no broken tests on the diff, then there are going to be some hard questions for the team that didn't write tests.

Ie, tests aren't mandatory, but if you aren't writing tests, it's your responsibility when someone else's change breaks your project.

That's the one I had. I got it from my friend in sixth grade, and who knows where he got it from!