AI for the win - online edit of handbook/troggle/trog2030.html

handbook/troggle/trog2030.html

@@ -40,6 +40,9 @@ there is such a lot going on we would create a large volume of software even if
   <p>Also, we do not use the database because we have have a lot of data (it's tiny), but because it gives us multi-user serialization.
     <p>So many of the previous efforts to "improve things" have been aimed at improving <em>the wrong things</em>.
 
+<h3>[ Update September 2025 ]</h3>
+<p>As <a href="ps2">Postscript 2</a> predicted, AI tools are now here and they can understand the troggle code and all the Django documentation better than our wildest dreams of only a few months ago. So the problem of requiring Django-competent programmers is now substantially reduced. There is now no good reason to abandon Django, and ongoing refactoring is now much easier too.
+
 <h2>Option 2</h2>
 <p>
 We keep the same architecture as now, and incrementally replace modules that use django/SQL with direct object storage of collections using pickle(), shelve() and json().
@@ -219,7 +222,7 @@ So a useful goal, I think, is to make 'troggle2' accessible to a generic python
 
 But even 'just Python' is not that easy. Python is a much bigger language now than it used to be, with some increasingly esoteric corners, such as the new asyncio framework.. 
 
-<h3>Postscript2 - end of 2024</h3>
+<h3 id="ps2">Postscript2 - end of 2024</h3>
 <p>The AI wave is just starting and <b>Option 3</b> could be just to stick with Django indefinitely and use AI programmer aids to help new coders understand and edit existing troggle. An AI can grok the whole thing.
 
 <hr />