Why not write him and ask? He stopped teaching because of a drop in demand. He clearly loves teaching. If you have a team to educate and a budget to pay him for his time and expertise, he might be willing to run a class for your team.
In practice, one would use energy recovery ventilation to exchange air with outside rather than a CO2 scrubber (not clear if you actually meant a scrubber).
I have been in some office buildings in United States which had CO2 monitors in each meeting room, and the ventilation would engage to control CO2 below a set level. We would entertain ourselves by exhausting our lungs onto the sensors to trigger the ventilation system.
The technical ability for the student to cheat in the present day is unprecedented.
For exams in most subjects, the cellular phone is held in the lap. The student needs only briefly expose the exam page to the camera of the phone: immediate photograph of the page, ingestion of the page by an artificial intelligence, and then: the student flips the page to view the side exposed to the camera, and glances down to see the answer on the telephone.
I ring a very nice bell and can "mute" the bell (touching it with my hand to stop the ring just after thumbing the striker), so when ringing for information rather than hazard, it's a short quick ring, rather than a long loud ring.
Signs here alert cyclists to warn when passing, so certainly this etiquette is considered normal, but also I imagine it is not universal to all regions.
Bicycle bells are mostly for warning pedestrians when approaching from behind and passing on shared-use trails. I ride on shared infrastructure and cannot afford to build new infrastructure when my town will not. Not warning a pedestrian when approaching from behind introduces the possibility of collision if the pedestrian makes a sudden change in his walking course. I typically use this etiquette:
Passing a single pedestrian or runner on a quiet day: no bell, coasting for a short bit with a loud free hub (the rotating ratchet element on the rear wheel) alerts the pedestrian to my presence.
Passing a runner: normal ring from a distance so they have knowledge that the bicycle is passing
Passing a cyclist: one loud ring from a distance
Passing a pedestrian walking a dog: two loud rings, one far, one close, so that the pedestrian is aware of the approaching bicycle and he can prevent his dog from running at me/colliding. Many dogs do seem to enjoy a bicycle chase.
Antisocial pedestrians (i.e., walking side-by-side such as to be blocking the path in both directions, preventing the bicyclist from passing): several loud rings of the bell until the antisocial activity has abated. Announcements in my local tongue (not English) that they impede the flow of traffic.
A source control tool such as git or mercurial will solve this. Any collaborator who uses vi should have no issues with a git/hg workflow for managing changes.
I am not convinced of the wonderfulness, because the study implies that AI does not improve task completion time but does reduce programmer's comprehension when using a new library.
>We find that AI use impairs conceptual understanding, code reading, and debugging abilities, without delivering significant efficiency gains on average.
>this error does make me pause to wonder how much of the rest of the paper used AI assistance
And this is what's operative here. The error spotted, the entire class of error spotted, is easily checked/verified by a non-domain expert. These are the errors we can confirm readily, with obvious and unmistakable signature of hallucination.
If these are the only errors, we are not troubled. However: we do not know if these are the only errors, they are merely a signature that the paper was submitted without being thoroughly checked for hallucinations. They are a signature that some LLM was used to generate parts of the paper and the responsible authors used this LLM without care.
Checking the rest of the paper requires domain expertise, perhaps requires an attempt at reproducing the authors' results. That the rest of the paper is now in doubt, and that this problem is so widespread, threatens the validity of the fundamental activity these papers represent: research.
Agree about the possibility of infra nightmare, especially in the "SVN era" -- but in 2026, it's pretty straightforward to run a gitlab instance (takes about an hour to set up, most of which is DNS and TLS stuff, ime) for a course and set up actions, or use other submission infra like CMU autolab. I do this.
Agree with your comment about probability, motivation, and skill.
Agreed: information-dense isn't bad at all. It's a reason for peer review, though: people other than peers in the field have a much harder time reviewing an article for legitimacy, because they lack the context.