Weeknotes #56 (November 29, 2025)
Posted on:
Things I found, read, did, and produced this past week.
Things I consumed
- There is a history manager to share terminal context across machines called Atuin and I recently learned that they have expanded their ecosystem into a native app Atuin Desktop that focuses on the idea of a runbook, which is in a similar vein to a Jupiter notebook of the Python world of intermixing documentation with executable blocks for repeatable processes. As wel, it has a Google Docs-esque collaboration workflow such that multiple people can develop these runbooks at the same time. I wanna try experimenting with this and see if I can take various repeatable processes and write notes for them as a way to self document scripts that I want to be involved in the runtime rather than just running a script to completion without any intervention.
- I've been noticing an uptick in AI generated PRs on OSS repos that have minimal work for review put into by the creator of the PR which is concerning. Rather than call out particular PRs or people, I want to at least push for these types of PRs to be scrutinized in the case that if you submit a code change with 1000s of lines of code changed and you can't reason yourself why they were done it, you as a contributor need to put more time into reviewing the code even before the PR is made. As well, if you're letting an AI write a huge feature for a large OSS project, there should be ample discussion beforehand between yourself and maintainers such that you don't throw up a PR that doesn't actually solve the problem. I'm not calling for all AI PRs to be completely banned, but the person opening the PR should heavily review the code they let a LLM generate even before it hits GitHub or other version control platforms.
- On the flipside, I've been watching the e18e team who are trying to cleanup / modernize the JS ecosystem work and started contributing to their Open Collective as I feel as the JS language improves a lot of code that was kept for backwards compatibility is no longer needed and the sprawl that is node_modules can be improved over time. Some of their best case studies include Storybook.js where as of their v10 release the dependency graph is 29% smaller than v9 which itself was 50% smaller than v8.