Unlike git-blame, which can tell you who wrote a line of code, git-who tells you the people responsible for entire components or subsystems in a codebase. You can think of git-who sort of like git-blame but for file trees rather than individual files.
-
Long article about why we should stop with Python
__init__. Yes I assure you, it can be interesting. -
Facebook motto is still doing damage:
The motto has an implicit preamble, āOnce you have done the work to make broken things safe enough, then you should move fast and break thingsā.
-
wrkflw, to test your GitHub actions locally. I couldn't make it quite work yet.
-
Do Dumb Things, the last speech of Armin Ronacher at PyCon Austria 2025
In short, every project should have what Heroku calls āReview Appsā. Every pull request gets its own deployed environment on demand, allowing it to be demoed and reviewed. Pull requests are only merged into master when they are ready to go to production, and theyāre reverted if they turn out to have been unready.
- And read this piece from Aftermath: āAn Overwhelmingly Negative And Demoralizing Forceā: What Itās Like Working For A Company Thatās Forcing AI On Its Developers