TL;DR --We have slowly been working on our portal in a bespoke manner. Ten years ago, there was lots of attention on the web in understanding HTML/CSS/JavaScript with examples provided by those who had the time and interest. At the same time, development in machine learning lead to thoughts of autocode (as in the machine doing the coding). Now, we witness countless offers for robotic development of software. Something is wrong.We will look at this, over time, since it's not of prime concern. Yet. Besides we will see shakeouts of methods which is normal for progress. Too, we have lots of pending work to do. One that is high on the list is getting regular attention to the date of the death (29 Dec 1674) of Thomas Gardner (Salem planter).
---
Want an example? Our Gardner's Gate or portal. We have used the phrase a few times but intend to use it more. Our first reference was this post in January of 2020: Gardner's Gate. In that post, we mentioned a few of the types of research that we were doing. At that time, we may have had some notion of the coming technology interest but did not mention the subject.
Guess what? A month later, we were informed that a city that we had visited had cases of confirmed COVID. Life changed, then, for a while, as everyone adapted to the new regime brought by the pandemic. For us, we got into research that was more involved (the US interior). One particular problem took us almost two years to resolve; but, we stuck to it and accomplished the necessary feats.
A little before, we had started the portal (https://TGSoc.org). That was in 2017. In doing so, we took advantage of some earlier work. But, we took a "bespoke" path and will continue.
Why mention this? Well, algorithms, computing, and such has been John's work in advanced computational systems. The TGS main blog started in the Microsoft world due to the influence of ASP.NET. There were jumblings in that world in 2012 to which we adapted by leaving the Microsoft realm and going over to a Linux server. By the time of the portal, we had a strategy (somewhat). We needed resources and continual involvement, but there were other factors controlling time.
For one thing, research came first. We have been doing issues of Gardner's Beacon and printed several releases of The Gardner Annals. There were meetings and research for other groups. But, as John worked the bespoke issues, he kept notes and published some of them (we intend to organize links to this material -- see Devlog).
Too, some organzational work became more involved taking time and energy. But, we kept the TGS, Inc. fires going. Until COVID came along and changed things. Eventually, those constraints went away; people started to get their lives back.
But, the underpinnings of technology were changing. We'll detail our views and experiences. But, GenAI/LLM appeared three years ago. Our first experience was with ChatGPT after which we settled with Bard/Gemini. It wasn't much later that we had looked at the problems with finding algebraic solutions (Technology and its influence).
Sometime later, interest in what's known as "vibing" to some came to be; too, using LLM as a tag, people began to develop methods that allowed the facilities to assist in development (co-pilot in some cases; in others, there is more autonomy). We will discuss this from the framework of maturity and dependable/stable computing.
So, bespoke will be spoken in our world.
---
Again, research? Thomas Gardner died 29 Dec 1674 (post written 3 Jan 2019). One of our research topics was, where is he and his remains? That topic will be mentioned yearly henceforth. We will put a page on this at our portal in the coming months.
Remarks: Modified: 12/13/2025
12/10/2025 -- Some edits of typos and adding new information such as a graphic.
12/13/2025 -- We started with Microsoft's Office on-line and its developer's tools. The intent was to carry on with the ASP.NET approach (I liked C#), even though my early web work was in Unix, for the most part. Office 365 came along; that was our first instance of seeing companies falter as they learned that their processes no long worked. What did we do? Surveyed the alternatives. Picked a Linux server. And, fell back to HTML where buttons were captured by image and the behaviour was coded using CSS. That worked. The next step was to covert to Javascript. That continues. The issue was content versus configuration and continues (AIn't notwithstanding - map/territory issues will be discussed) Our focus was content and still is except the AIn't emergence changes things. So, bespoke? We're putting out a new issue of Gardner's Beacon (Vol. XV, No. 1) and will be starting to redo our analysis. We'll report regularly as we go along. As we will stop and discuss choices in the vein of engineering tradeoff analysis.
No comments:
Post a Comment