Teaching Social Studies – Innovation Blog

Bounded AI in Education

Why We Design AI With Limits, Roles, and Instructional Purpose

One of the central ideas behind our platform is what we think of as bounded AI. In education, that matters enormously. The question is not simply whether AI is present in a tool, but how it is present. Is it open-ended, dominant, and difficult for a teacher to control? Or is it constrained by instructional purpose, teacher settings, and clear limits on what it is allowed to do?

Our view is that classroom AI should be bounded. It should serve the learning task rather than take it over. It should operate inside a framework defined by the teacher, the assignment, and the goals of the lesson. In practical terms, that means AI should not function as a free-floating substitute for instruction, nor should it become an unrestricted shortcut around student thinking. It should be structured, limited, and accountable.

That principle appears in several different ways across the platform. In some applications, teachers explicitly control how much student-facing AI is available by assigning a limited number of AI uses or “licenses” per student for a particular task. In grammar and writing workflows, for example, AI assistance is not simply switched on without limit. The teacher decides whether students receive access, how much access they receive, and when those counts should be reset or renewed. That matters because it keeps AI from becoming an ambient crutch. It remains a defined instructional support rather than an always-on replacement for effort.

Bounded AI also means constraining what the model is supposed to do. In the conversational tools, the AI is not treated as an unrestricted chatbot. It is given a teacher-defined topic, guidelines, and role, and it is instructed to stay within that frame. If a student tries to push the interaction off topic or get the AI to abandon its assigned role, the system is designed to redirect the exchange rather than reward the drift. In other words, the AI is not there to become anything the student wants it to be. It is there to support a particular kind of language practice under teacher-defined conditions.

That same logic extends into oral assessment. In the viva voce tools, the AI does not simply improvise a conversation however it wishes. It operates within a configured assessment structure. It is guided by the assigned topic, the intended proficiency band, the turn limit, and the instructional expectation that difficulty remain within a stable range. If a student struggles, the AI can narrow or rephrase. If a student is strong, it can deepen the probe. But it is not supposed to veer into a different topic, change the task, or suddenly raise or lower the level in a way that distorts the assessment. This is a very different educational use of AI from an open-ended chat experience. The AI is acting more like a constrained assessment instrument than a digital companion with no boundaries.

Bounded AI also means limiting the function itself. In our platform, AI is generally assigned a specific role: provide feedback on grammar, help a teacher score a rubric, summarize short responses, generate a draft activity, maintain a target-language interaction, or support a structured discussion. Those are narrow tasks. They are useful tasks. But they are not the same thing as handing over the intellectual work of the lesson to a general-purpose model. We think that distinction is one of the most important design choices in educational technology right now.

There is also a teacher-control dimension to bounded AI that is easy to overlook. AI can help generate drills, prompts, questions, and classroom materials, but those tools are still framed as teacher-facing publishing assistance, not as autonomous curriculum engines. The teacher remains the authorizing intelligence. AI speeds up drafting, variation, and differentiation, but it does not replace pedagogical judgment. Used well, this can feel less like surrendering instruction to AI and more like giving the teacher an on-demand assistant for producing customized materials.

The educational value of this approach is substantial. First, it helps preserve student thinking. A bounded AI tool can scaffold, redirect, or clarify without simply doing the work for the learner. Second, it keeps classroom tasks legible to the teacher. If the AI is operating inside a clear assignment structure, its effects are easier to evaluate and manage. Third, it makes misuse harder. Students are far more likely to offload cognition when AI is unrestricted, conversationally dominant, or available in unlimited ways. When AI is role-bound, topic-bound, use-limited, and embedded in task design, it becomes a support rather than an escape hatch.

Just as important, bounded AI supports better trust. Teachers are right to be cautious about tools that present AI as a kind of omniscient educational layer hovering over everything. That is not the philosophy here. Our model is closer to this: AI should enter the classroom with a job description. It should know why it is there, what it is allowed to do, what it is not allowed to do, and who remains in charge.

In the end, bounded AI is not a limitation in the negative sense. It is a design discipline. It reflects the belief that educational technology works best when it respects the shape of teaching rather than trying to dissolve it. AI can be useful, flexible, and powerful. But in a learning environment, its value increases when its role is defined, its scope is controlled, and its presence remains in service to human instruction.

Privacy by Design in Classroom AI

How We Limit Data, Bound AI, and Reduce Unnecessary Student Exposure

As AI becomes more common in education, privacy deserves more than a reassuring slogan. Teachers and schools need to know, in practical terms, how a platform handles student information: what it stores, what it sends, and what it deliberately chooses not to include.

Our approach is guided by a simple principle: use only the information needed to support teaching and learning, and avoid unnecessary exposure wherever possible. That principle shapes both the way accounts are managed and the way AI features are built.

At the account level, we keep subscriber records focused on essential information. A functioning classroom platform does need core account data, enrollment relationships, and activity records tied to real users. But that does not mean the student record should become a warehouse of unnecessary personal detail. We aim to keep the data footprint as limited and purposeful as possible.

Student access is also designed with flexibility and restraint in mind. In many parts of the platform, students can sign in using a standard email-and-password account. Where appropriate, teachers can also enable a class-number-plus-PIN login option. This gives teachers another controlled way to bring students into classroom activities without making email-based login the only path. PIN access is not open-ended. It is teacher-enabled, tied to classroom enrollment, and limited to active student accounts. In some workflows, it is also paired with session-token checks and lightweight challenge steps before access is granted.

Traditional account security remains part of that design. Password-based logins are supported, and passwords are stored as hashed values rather than plain text. The goal is to support real classroom conditions while keeping access bounded and appropriately controlled.

The same privacy philosophy extends into AI use. In many classroom AI workflows, the model needs the student’s work, but not the student’s identity. A writing sample may need feedback. A conversation transcript may need to be scored. A set of short responses may need to be summarized. In those cases, the instructional content matters; the personal name usually does not.

For that reason, our AI integrations are designed to scrub identifying information. When student work is sent for AI-assisted analysis, the focus is on the work itself rather than on personal identity. In discussion and transcript-based tools, prompts can preserve structure without exposing names by using neutral labels such as “Student,” “Peer 1,” “Peer 2,” “Poster 1,” or “Poster 2.” That allows the model to follow turn-taking, compare responses, and interpret interaction without requiring unnecessary identifying detail.

This is an important distinction. Privacy in educational AI is not only about preventing unauthorized access. It is also about reducing unnecessary disclosure inside authorized systems. A feature may be legitimate and still contain more identifying information than it needs. Our design goal is to keep asking that question: what does the model actually need in order to do the instructional job well?

That mindset carries across the platform. We try to limit stored data to what is functionally necessary, offer bounded and teacher-controlled access options, and structure AI prompts so they carry instructional signal rather than avoidable personal detail. In our view, privacy is not a single feature. It is a design habit.

No platform should treat privacy as finished work. Systems evolve, features grow, and safeguards need to be revisited. But the standard remains clear: keep data collection purposeful, keep access controlled, and keep AI use as privacy-conscious as possible.

That is what privacy by design means in practice.

Convo Application Walkthrough

One of the most practical tools in Innovation Assessments is Convo, our speaking task app built for teachers who want students to respond to prompts in a more authentic, manageable, and scoreable way.

At its core, Convo is simple: the teacher creates a conversation task using a sequence of prompt audios, students listen and respond one prompt at a time, and the teacher can later monitor progress, review submissions, and score the work using either simple prompt-by-prompt scoring or a fuller rubric workflow. But what makes the app useful is how much classroom reality it accounts for.

A teacher begins by configuring the task. The setup is intentionally straightforward: give the task a title, add context or directions, set an overall time limit, and decide whether each prompt response should also have its own time cap. That matters in speaking assessment, because sometimes you want students to think and answer naturally, not rehearse for several minutes. Teachers can also decide how students will complete the task. There is a browser-recording version for direct in-app speaking, and there is also an upload version for cases where device compatibility or student circumstances make recording in-browser less reliable. If a teacher wants tighter control, the task can require in-browser recording so response timing is enforced more strictly.

The prompt-building process is also flexible. Teachers can upload prompt audio files or record prompt audio directly in the browser while building the task. Each prompt can include a memo or script, which helps keep the assessment organized and teacher-friendly. This makes Convo work well for world languages, oral interpretation, speaking checks, listening-response tasks, and even teacher-created mock interview activities.

On the student side, the experience is designed to be focused. Students open the task, hear the teacher’s audio prompt, and respond prompt by prompt. The app supports real classroom constraints: access and visibility checks, timing, saved progress, and submission tracking are all built into the workflow. Students who have already submitted are not accidentally allowed to start over unless the teacher readmits them. That matters because speaking tasks can otherwise become messy very quickly if students are unsure whether they are still “in progress” or already finished.

Another strength of Convo is that it does not pretend every device behaves the same way. The app supports both browser recording and upload-based response collection, which gives teachers a practical fallback path when needed. In real schools, that matters more than elegant theory. A speaking tool only works if students can actually complete the task on the devices they have.

From the teacher side, monitoring is lightweight and useful. The teacher can open the monitor view and see which students are in progress, how many prompts they have completed, and who may need a readmit. This is helpful during live class use, language lab work, remote learning, or make-up assignments. The monitor is not overloaded; it gives the teacher enough visibility to manage the task without turning into a distraction.

Scoring is where Convo becomes especially flexible. Some teachers want quick scoring by prompt, especially when they are listening for completion, clarity, or general performance. Others want a more formal evaluation process. Convo supports both. A teacher can score by individual response or switch into rubric-based scoring, depending on how the assessment is designed. That means the same app can support quick formative checks and more structured summative speaking assessments.

There is also a strong accountability layer behind the scenes. Convo includes proctor-style event logging, submission tracking, and workflow protections that help preserve the integrity of the task. That is particularly useful for graded speaking work, asynchronous assessment, and remote completion settings where teachers want a clearer record of how the task was completed.

What I like most about Convo is that it is not built around a fantasy classroom. It is built around the real one. Teachers need prompt audio options. Students need a focused workflow. Some devices cooperate; some do not. Some speaking tasks need strict time limits; some need flexibility. Some teachers want quick scoring; some want rubric-driven feedback. Convo makes room for all of that.

In short, Convo is a speaking assessment tool designed for actual classroom use: easy to configure, realistic for students, adaptable across devices, and strong on both monitoring and scoring. It helps teachers move beyond “just record something and upload it” toward a cleaner, more intentional speaking workflow.

The Classroom Is Not a Game (and Not an Office Either)

Though retired, I still teach a few courses a day remotely. This week, I attended a professional development meeting for one of the companies for whom I teach, where a presenter used a popular interactive presenting app. The presentation itself was excellent. The app, however, was another matter entirely.

I will grant that, as a developer of educational technology myself, I am a harsh critic. But I suspect even the hundred and fifty or so others on that Zoom call would agree. The app was heavily gamified, filled with sound effects and floating reaction emojis designed to promote “engagement.” Each emoji triggered a popping bubble sound as it drifted across the screen. Participants continued clicking them even after being asked to stop, while the presenter was attempting to explain how to construct a complex AI prompt. The result was not engagement, but distraction.

My earlier posts have noted my long-standing skepticism of gamification. Its promoters often cling to the old trope that if students are having fun, they will not even realize they are learning. Forgive me for sounding like the old fogey that I am, but that idea has always struck me as pedagogically misguided. I want students to know they are learning. More importantly, I want them to learn how to guide and regulate their own learning. Attention should be directed toward the material, not toward points, sounds, or game mechanics.

If you explore the Innovation platform, you will notice that it is intentionally plain. Interactive tools include emoji responses, but they are subtle, silent, and easily disabled. This is by design. The platform reflects how I actually teach, rather than how a game designer imagines learning should feel.

Because most teachers are not developers, we often adapt software that was never designed for classrooms in the first place. We rely on office productivity tools or on educational software built by developer teams whose instincts lean more toward gaming than pedagogy. I occupy an unusual position as both teacher and developer, and I find great satisfaction in coding applications that behave the way a teacher actually needs them to behave.

The Classroom is Not the Office

Having taught since 1991, I have lived through the entire technological transformation of education. My first classroom had chalkboards and binders. My last, before retiring three years ago, had 1:1 student laptops and a SmartBoard. One persistent problem has been that much of our classroom software originated outside education, particularly in office environments.

When we placed laptops running word processors and spreadsheets in front of students, we gained powerful tools but lost a degree of visibility and supervision. In 1991, it was nearly impossible for a student to hide off-task behavior behind a notebook. In 2026, it may be a hidden browser tab. What was marketed as “real-world experience” often came at the cost of instructional control.

At Innovation, I aim to design learning spaces that originate in education rather than being imported from the office or the gaming world. Our writing tools include optional AI proctoring and live monitoring so instructors can observe student work in progress. Our assessment tools provide similar oversight, along with messaging features that allow teachers to guide, redirect, or support students in real time.

In short, the goal is not to make learning noisier or more entertaining. It is to make it more focused, more observable, and more teachable.

Good educational technology should not compete with the lesson for attention. It should support the teacher, clarify the task, and fade quietly into the background of learning.

After more than three decades in the classroom, I have come to believe that the best tools are not the loudest or the most entertaining, but the ones that respect how learning actually happens: through focus, guidance, and sustained attention. If our software cannot preserve those conditions, then no amount of animation, gamification, or sound effects will make up for what is lost.

Innovation 2.0

The few who read this may have seen the post a while back called “Sunset“in which I reflected on the difficulties and, well, failures I suppose of trying to develop an LMS as a small business without a huge bankroll for a coding team and marketing. In 2007 when I started this and made some money from my inventions, the internet was very different.

So then AI came along. There is plenty of material for blog posts on how this transforms my teaching (I still teach remotely part-time). The big effort for me was trying to devise ways to prevent or at least make difficult the inappropriate use of AI by my students. Interestingly, I turned to AI to do this.

Like my colleagues who did not just surrender to AI student work submissions, I first worked on changing how I designed my assignments. That only goes so far.

Next I rolled up my sleeves and started tweaking my own code in this platform which I use for teaching remotely. Things like timers, detailed logging and response of student activity in a browser, hiding things until time has passed, and eventually on to getting an API key from OpenAI so that I could add a button that would analyze the logged data from student interactions on the platform and understand likelihood of inappropriate usage.

Once I started tweaking my old code, I noticed increasingly that the AI I was using to correct it, making enhancement above my coding ability, was itself increasingly having trouble with old-fashioned and out of date coding practices in the Perl language. I asked it about this. It explained that the code base I had (which is admittedly 20+ years old) was out of date such that it would not support a moderate customer base. The database itself, holding the work of myself and customers some going back twenty years, had obsolete features beyond the scope of this post to explain. The work to re-code and update this was enormous and overwhelming. That’s when the “Sunset” blog was written.

But then I had a cool idea for an application. I needed a way to let my AP French students practice and be evaluated asynchronously for conversation skills. I wanted to write this in a modern way using up-to-date code base. I used AI to write it. I was not as proficient in PHP as I was in Perl. I was tired of coding and wanted to focus on curriculum development.

The result was smashing! And from there I kept building… Three months later, I have nearly completed Innovation 2.0. Wow. I have moved from coding myself to directing the AI to to the detailed coding. I am now the creative director, no longer consulting programming language manuals or searching stackoverflow.

What’s especially exciting for me is that the new software works exactly as I wish it to. And it’s all in one place! That was why I started coding 30 years ago anyway! I like to build and invent.

So in January I will be using innovation 2.0 with my own students to refine and debug it and then move customers over in February and start offering this platform publicly. There are great new apps I can offer, a fully-integrated AI support system with guardrails and controls, effective live monitoring and more!

🎧 Recording for Upload (Using Chromebook or Chrome Browser)

If you can’t use the direct browser recording feature, you can record your conversation using your Chromebook’s built-in tools (like Voice Recorder or Memos) or a free online recording tool, and then upload the file.

Part 1: Record Your Audio File

Open Your Recording Tool:
- Chromebook App: Open the Voice Recorder app or Memos app on your Chromebook.
- Online Tool: Open a new browser tab and navigate to a simple, free online voice recorder (e.g., searching “online voice recorder” will give several options).
Start Recording: When you are ready, start the timer or recording app and give your responses to the prompts in the conversation task.
Stop and Save: Stop the recording once complete. Look for a Save, Download, or Export button.
Name the File: If the tool prompts you, give your file a clear name (e.g., MyConvoTask.mp3). This makes it much easier to find later!

Part 2: Locating the Saved File (The Hard Part!)

Once you click Save or Download, the file goes to your local storage, most commonly the Downloads folder.

1. Using the Chrome Downloads Bar

After the file saves, you should see a small bar at the bottom of your Chrome browser window showing the file name.
Click the small arrow (⯆) next to the file name.
Select “Show in folder” from the menu. This will open the file explorer right to the location of your file.

2. Using the Files App

If the downloads bar disappears, you can find the file using the Chromebook’s file manager:

Click the Launcher (the circle icon in the bottom-left corner).
Type “Files” and open the Files app .
In the left sidebar, click on “My files” or “Downloads”.
Look for the file name you gave it (e.g., MyConvoTask.mp3) or look for a file saved right around the time you finished recording.

3. Uploading to the Task

Once you’ve located the file in your Downloads folder, you can go back to the Upload Version of the Conversation Task and use the Choose File button to select and submit it.

No More Lost Work: Introducing Automatic Versioning and Essay Recovery

We’re excited to announce a significant upgrade to our writing assessment platform: a robust, automatic versioning system. This change is designed to eliminate the anxiety and frustration caused by unexpected browser crashes, internet connection drops, or power outages.

This system ensures that if your computer fails, you can recover nearly every word you’ve written.

1. How the System Works: Two Tiers of Protection

We’ve implemented a two-tiered saving system that balances constant crash protection with efficient storage of long-term history.

Tier 1: Crash Recovery (Every 50 Seconds)

Our primary safety net remains the quick, frequent autosave.

Function: Every 50 seconds, your application sends your work to our server.
Purpose: This aggressively updates the main copy of your essay on the server. If your browser crashes, the most you can lose is the work you completed in the last 50 seconds.
Where it’s Saved: This content is saved to the primary database record, which is what your instructor sees.

Tier 2: Historical Versioning (Every 5 Minutes)

This is the new feature that protects against data loss and provides a long-term audit trail.

Function: Every 5 minutes, a separate, dedicated process takes a full snapshot of your essay.
Purpose: This snapshot is saved as a complete, new record in a separate History Vault. If a crash happens, you now have a series of historical versions (from 5, 10, 15 minutes ago, etc.) that you can use to piece together your lost work.
Storage Efficiency: To avoid using up too much server space, the system is smart. It only keeps the last 5 versions for immediate recovery.

2. Using the New Essay Recovery Tool

If your browser or computer crashes, you’ll find a new recovery button when you reload the writing task. This process allows you to retrieve a specific version and append it to your current working document.

Step-by-Step Recovery:

Relaunch the Task: Close your browser and reopen the writing assignment. The system will load the last successful Tier 1 save (up to 50 seconds before the crash).
Click the “Recover Version” Button: A new modal window will open, showing a list of available historical snapshots.
Review the Snapshots: The list will show the time and date of each of your last five saved versions (e.g., “Saved at 10:15 AM,” “Saved at 10:10 AM”).
Select and Append: Click the “Append to Essay” button next to the version you want.
- The system retrieves that entire version.
- It automatically inserts the recovered text to the bottom of your current essay, clearly marked with a timestamp (e.g., --- Recovered version (10:10 AM) ---).
- You can then quickly cut and paste the recovered sections back into the body of your essay.

Why Append?

We use the “append” feature to prevent accidentally overwriting good work. This method gives you full control, allowing you to manually review the recovered text and integrate it precisely where it was lost.

3. Best Practices for Test Takers

While this new system offers powerful protection, you still have a role to play in preventing crashes. The vast majority of work loss incidents are caused by an overwhelmed computer.

To ensure a smooth, crash-free experience, please follow these rules before starting your assessment:

Close All Unnecessary Tabs: Close all social media, streaming video services (YouTube, Netflix), and other assignment tabs.
Minimize Background Applications: Close file downloads, large games, or other applications that consume significant memory.
Ensure a Stable Connection: Although the versioning system protects against brief internet drops, a stable connection ensures your 50-second autosaves are always successful.

This system is now live and ready to keep your writing safe! Happy writing! ✍️

Chromebook Crash? Your Test Answers Are Safe.

We know that a browser crash—especially a memory-related issue on a device like a Chromebook—is the last thing any student wants to deal with during an important test or assignment.

We’ve designed our online assessment system with a robust, multi-layered data saving architecture to make sure that a client-side crash results in minimal, if any, lost work. The result? At worst, you might lose only the last few seconds of work on the single question you were answering.

Here’s a look at how our system ensures maximum resilience against unexpected interruptions.

1. Answers Save Instantly (Per-Question Saving)

We don’t rely on a single “Save” button or a large, infrequent auto-save. Instead, we use a technique called asynchronous saving that pushes your answers to our secure server the moment you make a change.

Multiple-Choice & True/False: As soon as you click an option, that selection is immediately sent to the server and recorded. Data loss for these question types is virtually impossible unless the crash occurs mid-click.
Short Answer & Essay: When you are typing, your response is saved frequently and on critical events (like clicking out of the answer box). This means the work you’ve completed on previous questions is secure, and only the latest few seconds of typing on the current question might be lost if the crash happens before the final save request completes.

2. Time Used is Tracked and Recovered

For timed assessments, losing time due to a crash is just as frustrating as losing answers. Our system actively tracks and saves your elapsed test time to ensure a fair recovery.

Periodic Time Logging: A small, background function logs the total minutes you’ve used to the server at regular, short intervals.
Seamless Resumption: If your browser crashes, simply closing the crashed tab or restarting your device and logging back in will resume your test. The system immediately retrieves your last logged time, deducts it from your original limit, and starts the countdown from your remaining time. You will see a “Resuming” message before you continue.

3. What Isn’t Saved (And Why It Doesn’t Matter)

While core data like answers and time are continuously saved, some non-critical, client-side items might be lost:

“Mark for Review” Status: Any questions you had flagged for later review will need to be re-marked upon logging back in.
Window State: Settings like “full-screen mode” will revert to default and will need to be re-initiated.

These minor losses have no bearing on your score or the integrity of the test. Our priority is making sure the data that counts—your answers and your remaining time—is secure and waiting for you when you log back in.

Sunset

Well, the advent of AI in 2022 was both a boon and a bane for Innovation Assessments LLC. As a boon, it was an opportunity to incorporate AI into our apps. As a bane, it meant the main source of our income, sales on marketplaces like TeachersPayTeachers and TeachSimple, were reduced considerably. I closed both accounts last week.

The effort to make Innovation a “going concern” has spanned 30 years under different names. FrenchRegents.com. MultiLilnguae.com. JonesHistory.net. TeachersWebHost.com. The idea was to develop a subscriber base to my applications, software built to meet real teachers’ needs, not what programmers imagined teaching to be like. I never had the capital to launch properly in a crowded marketplace.

I am retired from teaching now. My career ended officially in 2023. I continue to teach remotely a few hours a day August to May because it is a pleasure to teach. My blog posts hence will come from that direction now.

If you want to subscribe to Innovation, you still can. But I am no longer engaging in marketing to promote it. Hey, I gave it a good go! Last spring I made a pitch to a virtual school I work for. Having not heard back from them, I surmise that my impressive Teams presentation was not enough to sell the service. It’s okay. They did me a kindness to hear my pitch.

I started coding classroom apps in 1993 when the closing Air Force base in Plattsburgh, NY donated a dozen or so IBM 286’s to the Crown Point Central School, where I was working. I learned QBasic and wrote simple programs for practicing verb conjugation for French (I was a French teacher then).

In the late 1990s, I was coding in C++ using a Borland compiler. I coded a messaging app, a drill and practice program, and even a security app for Windows 95! I was part-time technology coordinator for the school.

In the early 2000’s while active on a forum for foreign language teachers, I was contracted by a school on Long Island to code a web app for their classes in a “smart classroom”. From there I developed FrenchRegents.com and then SpanishRegents.com and even GermanRegents.com. I made some profit, until Barron’s Regents review made their test banks public, so I shuttered that business.

In 2007, I closed down and frankly foreswore trying to make money coding. It wasn’t until 2011 or ’12 that I tried again. By then, I had switched to teaching social studies (2004 I made the switch). JonesHistory.net was born.

The pandemic really supercharged my coding. I needed apps for teaching remotely. This was shortly after I moved from TeachersWebHost.com to InnovationAssessments.com after consults with a small business specialist. The limited liability company was formed in 2023.

After I retired from Schroon Lake Central School in 2023, I started teaching online part-time for LanguageBird and for Proximity Learning. These continue to be a source of enjoyment for me and an inspiration for app development. Both let me use my own enormous library of teaching materials spanning 30+ years.

A few weeks ago, I did some research and concluded that, if Innovation was to have a future, it needed to be re-coded in a new architecture. I worked for a short while in Python and then in Laravel Blade (a PHP implementation). Oy. The learning curve was steeper than I was able to tolerate. Add to this that I really didn’t have a reasonable expectation of any commercial success for my efforts, I abandoned the effort. It was kind of hard, actually. I have been working to build this, one way or another, for something like 30 years. It’s not easy to switch gears, admit defeat, let it go. But as a matter of principal, I value letting go when necessary.

So, I continue to upgrade the Perl scripts to suit my needs for teaching remotely. It’s a pleasure and it’s easier now with AI assistance. But even ChatGPT, in analyzing my old code, noticied the antiquity. Today it made a a joke about my coding being “like Netscape 1999”. I laughed out loud and I lamented a little that a robot could jest about outdated code.

Reader, rest assured that despite that “ancient” nature of the code, I have secured it against dangers and if you are a subscriber you may be assured of security.

Reader, a lot of this is tied up in being 57 years old and seeing things fade away and change. At this point, I suppose I am grappling with that.