So I’m referring a number of articles that talk about it as “Listings”

So am I. I read that article as well and "Program listings" is IMHO definitive, a "program listing" is a list of the instructions in the program it is a term I used to use myself, it's just fallen out of fashion. In addition this article shows form feed paper with a snippet of the actual code, one line per instruction.

Also, it's nothing like Musk, maybe you don't work in the industry but a "Team lead" is a programmer, just with additional organisational responsibilities. If you read the rest of the article I linked there are those that consider her the first professional "Software Engineer", and mistaking a team lead for the only member of the team is a common mistake, especially when they were the first programmer hired for the Apollo mission, It's a mistake, I wouldn't classify it as a lie.

Docker-compose is a orchestration tool that wraps around the inbuilt docker functions that are exposed like "docker run", when teaching people a tool you generally explain the base functions of the tool and then explain wrappers around that tool in terms of the functions you've already learned.

Similarly when you have a standalone container you generally provide the information to get the container running in terms of base docker, not an orchestration tool... unless the container must be used alongside other containers, then orchestration config is often provided.

I don't know how old you are but when I was first introduced to programming in the early 80s all "source code" (Mostly basic and thus interpreted where program is the source code) was referred to as "listings" (this was when the main source of games were monthly magazines where you typed in a listing from a magazine and saved it to tape E.G.. The "Program listings" (as the Smithsonian calls them) seem to be print outs of the programs for verification purposes.

The process of entering was indeed handwritten, on specially printed sheets of paper that was then handed to a punchcard operator to create the cards (again according to the Smithsonian), But the stack of paper is clearly not those sheets as it is form-feed printer paper.

It is completely accurate that Margaret Hamilton lead a team, so while there are inaccuracies I'd say this not as much of a lie as just a combination of confused concepts,

I think it really depends what you value as a power user, many "enthusiast" features still need root access and that both limits your choice but also (almost) rules out utility features (that I, personally, view as a requirement nowadays) like Google Pay

If you're looking for "big iron" apps like photo editing and midi sequencers then memory and speedy storage would be a requirement (many of the "gaming phone" models satisfy this)

Not sure how the setup differs but ours does not work with chrome, only edge

Not necessarily, I'm using Pop!OS but my workplace AzureAD SSO mandates Edge on Linux so you're not safe.

Doesn't surprise me at all, the company I work for has gone all in with AzureAD SSO and that will only work on Edge (edge supplies info for the MS asset verification software that constantly eats my CPU) so now we can't use anything other than Edge for any internal service and need to develop for Edge if we are writing an internal tool.

Personally I always use containers unless there is a good reason to use a VM, and those reasons do exist. Sometime you want a whole, fully functional OS complete with custom kernel, in that situation a VM is a good idea, sometimes a utility only comes packaged as a VM.

But absent of a good reason, containers are just better in the majority of cases

I would hope this would be obvious to anyone. If your client can highlight which posts you have upvoted in the web and app UI then the fact that your user specifically upvoted that post must be recoverable from the instance server and thus must be recoverable by the instance admins. I would not expect anything different.