See https://jmswtlk.github.io/GitHub-ing/ (and https://github.com/jmswtlk) to watch progress.
Precursor to technical blogging that is following my introduction to GitHub. The idea here is that getting familiar with the cloud'd GitHub is being done with https://tgsoc.org as the focus. Or, our 'Portal to truth' with all sorts of meanings. I'll keep adding to the bottom until I work out a better method. See ReadMe for pointers to the work done to date. --- Will log here until I see how to do it better ---
1 - Uploaded the JS files. Now, see how to update and sync changes here at the FTP site. 2 - First branch and update. Now do a pull. Several other updates pending. 3 - Brought in more files. Like the interface. Got a project page started. Also, will be using Wiki (to have something familiar - have been hackign with textual editors primarily - content was the focus). 4 - With a better view than the little text window, I can see more noise put in. Interesting. 5 - Disclosure: my purpose was content which covered centuries along all sorts of threads. The computing aspects were considered secondary since information was the intent.
6 - Stopped to look at templates. Of course, ran into these when I was doing my occasional review of possible techniques. But, content was my focus at each of those points. Though, I did spend a summer doing a little codecademy every day, did all of their lessons at the time, while doing so opinionated about the experiment, wondered about the motivation behind some of those, they have proliferated madly, ..., mad house, anyone?, ..., even saw reference to the 'floor' which i'll go into further, artistic/technical, one split, sure, it's presentation versus compute, some trying to split, i say, parametric versus algorithmic, i see css as a huge parametric set, will go into this, ..., as mentioned was using Sea Monkey Composer, even Wordpad, and Notepad, ..., eventually let Chrome's tools do their thing, ..., btw, not only minimal in terms of resource, i've been working without ide support, down and dirty with the text, ...
7 - so, no confusion about details (know one, know them all, essentially), but went and searched on motivation for javascript templates, i'm always asking why? (it's not enough to say, money, power, etc. -- we're in a mess, people), up pops the discussion, hearing from those on both sides, and then see 'dust' (someone always does it right) as being in the middle, remember 'floor' in the future, for all computing levels we have this bifurcation, some try to bridge as i have the past ten years doing everything, at least, i know enough to know where i'm deficit, ..., yet, perfection?, let's discuss that as one manufacturer who touts this (their mantra of is no failure is way beyond six sigma), has let software and its complexity get the better of their process with recent failures in a hugely public and tragic sense (think, falling out of the sky), ..., come one, people, we need to step back a decade and one-half and review what all of this endless permutation has wrought. 8 - also, i may be new to github in the sense of having an account, i'm no newbie to computing having watched, and participated in, its evolution, up close, for decades, in the trenches, not in academia, though i have worked with very many academics who stooped to see what we real-world people were up to, ..., more, ...,
9 - this is 8/12/19 8:02 (middle of the country) -- Oh yes, time. It flows too fast for the gold guy. Well, seems that the reading last night was from the 2013/2014 timeframe. Well, not too bad. Then, I looked at the template'd and bounced out. I had to do logic. Purtiness? We'll get to that. So, I come forward in time 2018 and then 2019 with a couple of stops in between. Ah, literal template. Yes. Then, HTML template. Wait, I could have used that rather than the hidden variables. But, again, when one is rushing configuration in order to work content, one minimizes. ... Don't have time, like some of these kids, to just play with code. ... Actually, never did that as I was always on an advanced team solving real problems. Albeit, we did get to SEI CMM Level 5 in that type of dynamic environment that involved products with a long timeframe. Why the rush? ... Schedule always was a huge factor.
10 -- I think, I'll be here for a few days getting things in order. Then, we'll be making changes and pushing them out to the website. Haven't mentioned it, but there'll be a Quora aspect to this work, to boot.
11 -- Need to go through these. https://colorlib.com/wp/top-templating-engines-for-javascript/ Already know about mustache and a few others. We'll plan to update our main site, too, https://thomasgardnersociety.org after we relook at its history from aspx to about 2016. I see some of the templates are oriented to languages of interest: Julia, Common Lisp, ...
12 -- Packages, announced within the past 3 months, latest information about template use, javascript, ..., github's collection of user experiences, etc., ..., impressive, ..., will be creating another project, soon, plus put a blog into place to carry the theme, ..., lots of things to discuss, why do we what we do?, how do past choices impact us now? (software focus, of course - essentially, truth engineering),
13 -- Created the GitHub'ing project for handling overview issues. One of these will be a relook at the movement from .NET (aspx) to Linux/HTML to html/css/js in the context of the PortalToTruth. Then, there will be a recap of 30+ years of AI, in the trenches. Meaning, of course, commercial environment where we were resolving real problems in a timely manner using AI techniques that still have potential life. Perhaps, a hybird view might be necessary in order to integrate with new kid on the block that looks a little overbearing, quite frankly. Lots to discuss. Next step is to create a blog here.
14 -- See the following Notes with respect to technical activity. As well, the overview discussion is at our Portal to Truth: https://tgsoc.org/.
Note:
08/27/2019 -- Looking to get the Actions (beta) going.
08/16/2019 -- Got GitHub'ing set up with our own format from the PortalToTruth. Will review this for improvement after doing a process review. Notes will be posted at the public page while re-organization goes on.
09/07/2019 -- Last two days show that I can get away. 30 days, tomorrow; all active, except for 2.
09/17/2019 -- Several items pending with some notion of priority coming to fore. Resources, mostly time, are always an issue.
11/21/2019 -- Started using 'md' for a blog for GitHub'ing which is the technical branch for this portal. We are working ot integrate our blogs which are on different platforms. We need to look at using our own (virtual) host, too.
12/11/2019 -- Finally bit the bullet and am rolling the text of the main page (similar to text scroll). Will allow an edit of those entries so as to remove the 'noise' of Composer of Sea Monkey. Looking for a good HTML editor which puts out clean code. We have 400 years to cover of a slew of families. If you're interested, Google Mayflower 2020, as the boat came here in 1620 (that is, Cape Cod area).
12/16/2019 -- Got 'er done, finally. This am, figured a good way to share an index across functions on the same page. Using a hidden div allows one to stack some parameters which can be popped off. Will push up tomorrow. Doing the work in HTML in order to get good formatting. So, how ought one like to compose prose in that environment? Cannot do it. Same goes for code. It has a hat. We have several hats that need to be given time in use. More later.
01/18/2020 -- Had a discussion about presence, now and future. Lots of options exist. Many older organizations are having a tug-of-war twixt the newer and older members. In one case, there is long heritage with an associated database that has slowly built up and that is considered reliable in terms of its information. Changes go through a long process for verification. That is unlike the wild flow of lots of information on the internet, that we know, increasingly, is suspect, even dangerous. We're going to be addressing core issues in that regard.
02/06/2020 -- A key word is 'interactive' in the sense of 'proof' which bears some discussion. https://en.wikipedia.org/wiki/Interactive_proof_system MIP and NEXP mentioned in a recent ACM Communications article on quantum computing.
12/15/2020 -- One man band, for the most part. Looking for technical talent with an interest in the broad interest of the Thomas Gardner Society, Inc. Technical, for us, means more than software or the computational aspects, as they are mere tools to an end. We have to discuss what those ends are (several) as well as the means associated with them.