Sutro Baths

One of the skills involved in pair-programming with the machine is to know when to do a major compaction.

It is, roughly, the milestones of a waterfall project-management approach. 🤖( the Waterfall methodology follows a linear, sequential approach to project management. It is structured around predefined phases, such as requirements gathering, design, development, testing, deployment, and maintenance. Each phase must be completed and approved before moving to the next, which makes Waterfall highly predictable and easier to plan. However, this rigidity can pose challenges in adapting to changes or incorporating feedback once the project has moved past certain phases. Waterfall is best suited for projects with clearly defined objectives, stable requirements, and minimal expected changes. ) 💡( It is not exactly that; Waterfall in the literature is something of a straw-man. What it is, is a series of changes based off an old version of the code (version 3). Once the cumulative changes become too much to describe, one must make a new version of the code (version 4) and start over.)

Some of the features in the last iteration:

• Moving web handlers to "blueprint" files rather than server.py. 💡( I find myself wanting to re-invent the header file. I only want to have the machine read 3-5KLOC, and using header files can decrease the LOC by a large factor.)
• CSS/JS fixes. Color-text is now default invisible, the sigil appears in a box. 🔥( there is code trying to rotate the sigil when it is clicked on. It doesn't work. I don't know if I want to enable it.)
• Login fixes. Users can login now, as long as they are the one user on the Google Auth whitelist.

The new "lexer" was written by Claude. But it fails many tests, so it is not enabled yet. 💡( this is a feature that will benefit from the extra screen-space of AppleVision.)

We also need:

• Print mode (and dark mode).
• various "two-column" views
• other features, as needed.