Though it was only a few years, it now seemed like forever since the Technological Fantasies organization had been created by Ann Kelly, Sally Aston and Drake Phillips. Their software was developed about the same time that a younger Beth Green had been developing hers, though hers was released later. The much more limited Project Match software had been made available about the same time as Beth’s.
These were the open-source projects of note. There were a few others, not so far along, and a few commercial endeavours which were not conspicuous successes.
All of these software projects or packages supported matching for various purposes and had other functions. They were used for social networking, interpersonal matching for various kinds of relationships including simple friendships, career management, education, various law and government functions, and planning for social change.
To do these things, the software had to maintain a dialogue with the user, accept questionnaire responses, ask for additional information, make suggestions, collect data from educators by providing them software support, and process social survey data.
Social Tech High was a product of the Tech Fantasies organization and used their software, though these three big open-source projects had database merging protocols and did indeed share data.
But now was time for a change. Beth Green and the Project Match founders, Don and Helen Walker, were now tied to the school through through short chains of individuals who were actually at the school. Each chain within the school terminated in a final teleconferencing link, which crossed the geographical distance separating these important individuals, who now joined Social Tech High in an active way. Each of the the Walkers, for example, were linked to highly compatible students and served as individual tutors for them, as well as becoming friends.
With such close links, software changes were inevitable. Beth was justly proud of her system, released when she was 13 after three years of software development, the system called simply The System.
The Tech Fantasies Trio and their colleagues were also proud of their software, though it had somewhat different goals. The Walkers and friends at Project Match had software aimed at matching alone and were perhaps somewhat less devoted to the software itself, but were extremely proud of their carefully constructed questionnaires.
It was Drake Phillips of Tech Fantasies who had perfected the interactive generated-question dialogue approach to gathering data. With it, there was no need of any questionnaires at all. He did not want to push to hard, but felt that what he had made the Walkers’ questionnaires unnecessary.
However much they favoured their own approaches and products, these were all quite easy going people, who would not push their views very hard. Sarah Rivers was the hard nosed one, not the only strong person in the collection of individuals, but the most determined, though she herself wrote no software.
“It’s fundamentally the same thing we discussed with data sharing. We each have our body of users. I for one will not let ours be compromised. We must continue to support them in all ways. No matter what we do for the school, we don’t change what our users have.”
“But Mommy, believe it or not, my system is not perfect. I was exaggerating. We could do better for the school, then maybe propagate the improvements.”
“I agree with both of you, ladies”, Don Walker said, “We can’t do anything too drastic that our users would see as a betrayal. Let’s not be like Microsoft. And Beth, yes, I am sure we can produce an improvement, if only for the school. Then if it is good, we can propagate it throughout our systems, somehow. I am not sure how, exactly.”
Sally Aston had a suggestion. “Well, we could have alternative user interfaces, for example, or partial alternatives. We could have a set of switches. If all are set one way, it is Beth’s system. If all are set the other way, it is our system. But the switches can be independent, allowing the user a choice.”
“As long as the user can load and save sets of choices under different names, I am all for it”, Don said.
“OK, now for the hard part”, Beth announced. What do we do about the new software? For the school. We should be able to improve on what any of us have, but how?”
That conversation, by video-wall teleconferencing, led everyone to agree to the same proposal. Each of them should do a lot of reading. Documentation reading, code reading, questionnaire reading, anything that would help them decide what to do.
Questionnaires were definitely to be considered. Although Drake had written his dialogue system to replace the questionnaire approach, he was finally argued down to the position that questionnaires were a useful alternative to his dialogue approach and even better as a prelude to it.
Nobody had given as much thought to questionnaires as had the Project Match people, so where questionnaires were to be used, theirs were the preferred ones.
Beth’s system and the Tech Fantasies collection of software were the source of the most controversy. Beth Green called her system The System because it was intended to be a single uniform system which could do everything. It could, for example, be an operating system for a computer. A carefully written subset of it, designed to be integrated into the larger whole could actually be the Basic Input Output System for a computer, its BIOS.
Beth claimed she had something in longword microcode to drive an array processor, and something to be layered onto silicon, as well.
At the other extreme, The System was in theory capable of reorganizing whole countries, perhaps the world. OK, Beth was an ambitious kid.
An entirely different approach had been taken by Tech Fantasies.
Ann Kelly was a brilliant pure mathematician, though she could program computers well too. She could design algorithms using sophisticated applications of what used to be treated as only pure mathematics, such as abstract algebra and topology.
Drake was adapt at turning algorithms into code, as well as designing them himself. When the algorithms involved a lot of numerical methods, he could rely on Sally, for that was her specialty. The three were an almost perfect working unit, which is why they had been employed to function that way when working in the software industry.
The three had not written a system, in Beth’s sense, though they did have software to do interpersonal matching and perform the other basic functions. Rather than a system, these were separate programs. The basis of these programs was a collection of lower level software libraries designed for such functions, but excellent for incorporation into other other programs. They had written good clean code, beautiful well-documented code, with flexible interfaces, easy to integrate into various applications.
“Alright, I have to admit you guys are brilliant”, Beth commented after reading a lot of Tech Fantasies code. She could read it the way ordinary people read prose. “My system was written by me for me. For our users, that is to say. And for me to maintain. It has clever code in it, in my humble opinion, but well, it’s not always clean and certainly not well-documented. So yes, it could be improved by using the Tech Fantasies software libraries. It might not be as fast, but it would be better overall and easier to maintain. Perhaps even extended.”
An obvious software integration strategy thus appeared. Use the libraries of nice clean code written by Ann, Sally and Drake to rewrite Beth’s system, which did seem to have the most power, and then incorporate the Project Match questionnaire database into the final result.
But who would do this massive integration task? Beth consulted her system. The trio consulted theirs. Finding the right people to work on a project like this was not the kind of task suitable for the Walkers, but they kept an eye on everything. It was just as well that they did.
The answer that finally merged was a “class” in the Social Tech High sense, that is to say a teacher, who might not really teach, and eight students, would would indeed do various kinds of work.
The “teacher” chosen turned out to be a young woman who had only recently completed her undergraduate degree. Wise and knowledgeable beyond her years, this fine person was the shy musician Helen Walker, who had an interdisciplinary degree in mathematics, psychology and sociology. There had never been any need for her to study music.
The “students” in the class were indeed students, eight of them, all good with software. Of various ages, there was, unintentionally, at least one from each grade in the school. Together they would do the far from trivial work of rewriting Beth’s code to make the best use of the Tech Fantasies’ software libraries.
It was agreed that the part of Beth’s system which was indeed implemented on silicon could be simulated in software for school use. Using the latest generation of silicon compilers, Beth had designed a wonderful processor chip in which, for example, there was a single machine instruction which meant extract these rows and columns, specified by 128 bit integers, from a database at some global location, specified by 512 bits, reformat this data according to specs at a second global location and store the result at a third. Her father owned a chip fabrication facility, a billion dollar investment, so he’d made her some.
By global locations, well, global. Anywhere on the Internet, any computer, hard-drive, directory, file and byte. Suitable defaults coded, to refer to current file or the specified supersets. Other machine instructions were of equal power. Yes, they’d simulate those in software.
When the class was at work, Helen Walker would use her own home video wall to communicate with the students, who would be well rewarded for their work.
Beth’s system was written in her own language, PreCode, which did build in very limited amounts of documentation in function call names. For this new project, she compiled it into C, the language the Tech Fantasies code was written in, her call-by-name parameter names turning into brief inline comments. The software team compiled Beth’s code into Python libraries and called them from Python, recreating the system in a more modular format. After that, the libraries based on Beth’s code were pulled out and replaced by the very pretty Tech Fantasies libraries.
The result of all this translation and coding would soon appear. It would have many extensions added to the code from various pieces of Tech Fantasies software. The Project Match software would just be simulated, however.
As agreed upon, various switches were provided to permit the resulting system to look like any one of the original three systems, but a specific selection of these switches was written out in a file labelled “Social Tech High Software Setup File”. Except for minor changes this would be used for a long time to come, as if it was the school’s own software package. In every practical sense, it was.