Anki-Android VS configs

Yes, but on Android you currently have to sideload the 2.17 alpha from this page: https://github.com/ankidroid/Anki-Android/releases

If that fails, report an issue, including debug information and the deck: https://github.com/ankidroid/Anki-Android/issues/new/choose

But you can just download the testing version from the links to github on the site. https://github.com/ankidroid/Anki-Android/releases

Good news again, AnkiDroid has completed its Rust backend update. FSRS will be supported in AnkiDroid in 2.17.

GitHub: https://github.com/ankidroid/Anki-Android/releases

I was a long time pre-commit fan, just converted to https://trunk.io/ though

Trunk | https://trunk.io | Sr Full Stack / Sr C++ | Full-Time | Remote / Hybrid, SF

Trunk is an a16z funded dev tools startup, redefining software development at scale. We've built three products so far and have plans for more:

* Trunk Check: a universal linter/formatter, available as a CLI, VSCode extension, and CI check;

Trunk is also a command line tool, so you can run all these checks on CI, with the same versions of tools you use locally

Tests are a good way to assert an invariant that you expect of your codebase, but as with all things, resolving the error can get a bit tricky/frustrating.

The canonical example in my mind is any kind of autofix-able linter, where there's some kind of patch (or more nuanced autofix) that the linter can generate on-the-spot for you. With a sh_test construct (or any other unit test), you generally find yourself printing out some command that the user can run to fix things, which in a sufficiently large codebase can get really frustrating.

(My company - https://trunk.io - is actually building a universal linter as part of our product offering, and we already have a system to write custom linters with varying levels of sophistication that can plug into both your IDE and CI system.)