Mainly the official git CLI for controlling branches and sub modules, and sometimes the GitHub CLI if quickly checking out a pull request from a forked repo.

Also use the source control tab in VSCode rather often, as it’s really convenient to review and stage individual line changes from its diff view, and writing commit messages with a spell check extension.

If it’s a big diff or merge conflict, I’ll break out the big guns like Meld, which has better visualizations for comparing file trees and directories.

About a decade ago, I used to use SmartGit, then tried GitKraken when that came around, but never really use much of the bells and whistles and wasn’t keen on subscription pricing. Especially as the UX for GitHub and other code hosting platforms online have matured.

What user software are folks using to monitor and log PSU sensor data?

Would be nice to correlate power usage and efficiency with system load percentage over time and type (CPU vs GPU).

I hope this rust library can make its way back into Moonlight and Sunshine projects.

I’m waiting on support for inserting PDF figures, the most common format my tools export.

• https://github.com/typst/typst/issues/145

What about carrying on a legacy with maintaining a intergenerational codebases? Like from a family owned business, a FOSS project, or hobby video game? Something that span’s across tech stacks, historic trends, and familial code authors, like the ship of Theseus crossed with Noah’s Ark (built with the help of Noah’s entire family over almost 100 years, as the theological mythology goes).

You know how folks inherit tools, workshops, or auto projects from parents and family? Stuff like wood working equipment, sewing machines, or whatever tools of the trade. It’s got me wondering, what’s it like for children that inherit their parents’ codebase, computers, keyboards. Surely with the growth of the tech sector and job market, compared to half a century prior, this could be a growing re-occurrence.

E.g. like the entire premise of this YouTube channel titled “Inheritance Machining”: https://youtu.be/hearLttbrLo

For example, my grandfather worked for IBM, and my family recalls growing up surrounded by punch cards around the house. Of course that form of programming only lasted so long, so the next generation was unlikely to reuse the same tools of the trade, but as tech stacks have matured and interfaces standardized, what are the chances are that folk’s children will use the same Linux kernel modules, custom mechanical keyboards or desktop chassis that their parents used today?