HN user

amethyst

5,170 karma

https://amethyst.cat

amethyst at n7.gg

Posts2
Comments77
View on HN
  Location: California
  Remote: Yes
  Willing to relocate: no
  Technologies: Python, Rust, SQL, fullstack
  Résumé/CV: https://amethyst.cat/resume
  Email: amethyst@n7.gg
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.

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.

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 ;)

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.

My 2017 Golf R would intentionally turn off the dashboard backlights at night if the lights weren't on, providing me excellent feedback that they weren't on. Either head lights should always be on auto by default, or more cars need proper feedback to the driver when they aren't.

Python makes it incredibly tough.

I disagree, Python makes it incredibly easy to work with threads in many different ways. It just doesn't make threads faster.

I wish I could selectively disable only the "paste" events, because it's extremely useful to have "click to copy this value" type of buttons in our various work tools, and I miss the ability to do that every time I try turning off clipboard events to deal with bad actors.

Python, JS, C, Bash aren't even particularly great at the problems they solve

I would argue the "problem" that Python really solves is the amount of engineering effort required to read and write code for common software use cases. Ie, it's purpose is to help developers write better code faster and easier than other languages, while execution speed has usually had a lower priority. In that framing, it's great at solving the problem of development time and old code being hard to maintain, and that's why so many engineers like myself love it.