amethyst · HackerTrans

vor 23 Tagendiscuss

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.

amethyst

letzten Monatdiscuss

  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.

amethyst

vor 3 Monatendiscuss

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

amethyst

vor 3 Monatendiscuss

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

amethyst

vor 5 Monatendiscuss

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.

amethyst

vor 7 Monatendiscuss

It works pretty well for Apple

amethyst

vor 7 Monatendiscuss

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

amethyst

vor 3 Jahrendiscuss

Keep in mind that many/most of these tools also need to work in diff review and CI tools, not just in an editor. That said, we primarily support developers using VS Code (with internal LSP/plugins/integrations) or our internal version of Jupyter notebooks. We also have a non-negligible number of folks that prefer alternative IDEs or editors like pycharm, vim, or emacs. We try to build our tools such that they are accessible by CLI or APIs, so that they can fit into any of these systems as needed.

amethyst

vor 3 Jahrendiscuss

The Cinder team's longterm goal is to upstream as much as we can, and make the rest available as pip-installable extensions that anyone could theoretically install and use on CPython. The fewer internal changes and patches we need to maintain, the faster we can adopt upstream Python releases and all of the associated performance and tooling wins.

amethyst

vor 3 Jahrendiscuss

It's mostly foundational work around developer tooling and infrastructure that isn't already covered by other dedicated teams (eg, there is a dedicated Cinder team). My latest work has focused around formatting and linting, and includes open source work on µsort, our import sorter [1], and fixit, our custom linter [2] that makes it easy for teams to build and deploy their own custom lint rules with autofixes.

Some of my team mates work on driving internal adoption of Cinder, rolling out new versions of Python everywhere, improvements to our build and packaging systems, supporting other Python tooling teams, etc. There's a lot of cross-functional project work, and our primary goal is to improve the Python developer experience, both internally and externally wherever we can.

1: https://usort.rtfd.io

2: https://fixit.rtfd.io

amethyst

vor 3 Jahrendiscuss

I'm not familiar enough with Django to say for sure, but I assume at this point it's almost entirely custom ORM and libraries on top of async django routing/response.

amethyst

vor 3 Jahrendiscuss

It's a heavily modified internal fork of Django. Source: I work on our Python Language Foundation team.

comments