Your concept of "every level of understanding" does embody the PM stereotype. From an engineering perspective, most of your list tends to be 90-95% timewasting fluff and toil. Hopefully with as much as 5-10% valuable content that can help the team to accomplish their mission.

A good PM (IMO) would take responsibility for dealing with the fluff, and engage the TL with the 5-10% useful fraction.

Also, a good PM will strive to learn and understand what the team is doing and why... well enough to act as an advocate for the team, and explain to the many people you interact with throughout the organization.

A team will respect and appreciate a PM's effort to meet them on some technical level of understanding. Being embedded with a team of experts in a particular technology gives you a unique opportunity to raise your understanding of their tools, technology, tasks, challenges, and successes.

A good PM is valued as a colleague contributing to the team's success.

Shortly after the video was shot, this panel was decommissioned and removed. In 2018 it was brought back to life at the Didcot Railway Centre [2], where it continues in operation, backed by a simulator. Centre visitors can try their hand at operating the panel [3].

The panels "utilise square tiles called ‘Dominos’, patented by a Swiss company called Integra, to construct the panel diagram. Each Domino is 40mm square and has a small section of the layout on it, such as one signal, or one set of points. Many hundreds of small Dominos are then formed into a mosaic to build up the required panel diagram." [4]

Photo gallery [5]

[1] https://www.youtube.com/watch?v=76fAHAxv0Dw

[2] https://didcotrailwaycentre.org.uk/article.php/116/the-signa...

[3] https://www.youtube.com/watch?v=S1Jfm9Zqo_M

[4] https://didcotrailwaycentre.org.uk/article.php/680/more-abou...

[5] https://photos.swindonpanel.org.uk/

"Python for Data Analysis" by McKinney (2018)

"The Go Programming Language" by Donovan and Kernighan (2016)

"Hacker's Delight" by Warren (2013)

"Algorithm Design Manual" by Skiena (2008)

"Purely Functional Data Structures" by Okasaki (1998)

"Structure and Interpretation of Computer Programs" by Abelson and Sussman (1985)

Also, in the Quick Filter, you can click the star button to "Show only starred messages".

Why are stacked commits useful? Multiple patches can be developed concurrently and efficiently, with each patch focused on a single concern, for a clean Git commit history and improved productivity. The tutorial [2] says:

> One common use of StGit is to “polish” a Git branch before publishing it to another public repository. The kinds of polish that StGit can help with include:

    Complete and correct commit messages.
    Each patch limited to one coherent topic.
    Each patch standing on its own: passing tests, etc.
    Considerate patch (commit) order

> As a concrete example, consider a situation where several Git commits have been made in a repository with commit messages such as:

    “Improve the snarfle cache”
    “Remove debug printout”
    “New snarfle cache test”
    “Oops, spell function name correctly”
    “Fix documentation error”
    “More snarfle cache”

Originally written in Python (2005, pre-GitHub) by Catalin Marinas, the current version is in Rust. StGit is free and open source [3]. It was inspired by Quilt [4], an earlier system credited to Andrew Morton and Andreas Grünbacher.

[1] https://stacked-git.github.io/ [2] https://stacked-git.github.io/guides/tutorial/#development-b... [3] https://github.com/stacked-git/stgit/ [4] https://en.wikipedia.org/wiki/Quilt_(software)

[0] https://www.usenix.org/system/files/conference/usenixsecurit...

Cox writes: "The main idea of this post is to implement fast unrounded scaling, which computes an approximation to x · 2^e · 10^p, often in a single 64-bit multiplication. On that foundation we can build nearly trivial printing and parsing algorithms that run very fast. In fact, the printing algorithms run faster than all other known algorithms, including Dragon4, Grisu3, Errol3, Ryū, Ryū Printf, Schubfach, and Dragonbox, and the parsing algorithm runs faster than the Eisel-Lemire algorithm. This post presents both the algorithms and a concrete implementation in Go. I expect some form of this Go code to ship in Go 1.27 (scheduled for August 2026)."

[1] https://research.swtch.com/fp

For $99.95, you can own an exquisite 0.75m USB-C 2.0 "High-Definition Audio Cable" [1], featuring "high-purity 0.5% Silver conductors and a Metal-Layer Noise-Dissipation for the most efficient dissipation of radio-frequency noise."

It has "Direction-Controlled Conductors: All drawn metal strands or conductors have a non-symmetrical, and therefore directional, grain structure. AudioQuest controls the resulting RF impedance variation so that noise is drained away from where it will cause distortion. The correct direction is determined by listening to every batch of metal conductors used in every AudioQuest audio cable. When applicable, arrows are clearly marked on the connectors to ensure superior sound quality." Power Delivery: No. Country of origin: China.

My web search didn't reveal any $1000 USB cables - doubtless those are offered only privately to the most discerning connoisseurs.

[1] https://www.audioquest.com/products/forest-usb-c-c-digital-a...

Personal care products - shampoos, soaps, lotions

Nutritional supplements

are counterexamples

[1] https://www.localcdn.org/

[1] https://github.com/Cookie-AutoDelete/Cookie-AutoDelete

Those cameras are for traffic detection, so the signal can turn green when a car comes. They aren't reading faces.