Like most organizations, the university has what I call administrativemanagement systems , the computers thathandle core business record keeping like payroll, accounts payableand receivable, HR, and (this being a university) crucial studentinformation like enrollment and marks. This is serious stuff, runusing expensive software on expensive databases on expensive hardware(and behind paranoid firewalls), and, like most places, is considered apretty crucial thing.

But it turns out that it has quietly become not the most crucialsystem the university runs.

Over the course of the Python code that I've written, I've noticedcertain patterns that seem to reoccur relatively frequently. One ofmy common ones is a pattern that I'll call the Mutating Proxy.

Python doesn't have much use for plain proxy objects, objects thatjust relay things to another one, since duck typing means that you canusually just use the original object instead. A mutating proxy is aproxy that's used in order to change the behavior of the underlyingobject,

One of the things that irritate me about ZFS is the interactionbetween snapshots and quotas, specifically that ZFS snapshots countagainst a filesystem's quota. I can only call this robot logic ; it is in a sense completely correct and itprobably simplifies the implementation, but it is not useful .

The problem is that snapshots are a system level thing; having themcount against user quotas is a problem waiting to happen. Considertrying to explain to a user that they have 'run out' of disk spacebecause the