The author writes detailed Python articles on standard library design, asyncio, performance, and when to use classes.
HN commenters recommend it as a clear, empathetic guide for newcomers, and the author links their own posts to explain design choices.
I do like "just" being suggested, but I strongly prefer using a very simple bash run script for tasks that do not require "make"'s extras, especially given that most modern build tools do parallelism and artifact caching internally.
Inspired by:
https://github.com/adriancooney/Taskfile
https://death.andgravity.com/run-sh
I wrote an entire article about why I didn't do that: https://death.andgravity.com/own-query-builder#sqlalchemy-core-peewee-query-builder
In general, SQLAlchemy is an excellent choice; in my specific case (single dev with limited time), the overhead would be too much (even with my previous experience with it).
Have you read this? It's one of the few I've come across that has the appropriate degree of empathy for the confused newcomer + actionable advice:
https://death.andgravity.com/same-arguments
And it doesn't fall into the "Dog inherits from Animal" taxonomic crap.
They did mention they tried that, and got similar results to the binary search they were already doing: https://death.andgravity.com/pwned#position-heuristic
Indeed that's discussed in the article, under "Position heuristic" - https://death.andgravity.com/pwned#position-heuristic
They actually discuss that: https://death.andgravity.com/pwned#position-heuristic