Architected Futures™

Tools and strategies ... for boiling the ocean

Tickler Feature

This isn't a conventional web site. We need a feature, maybe along the lines of moodle, so we can track areas and subjects that have been read on a scatter shot basis. The same system can bookmarked for highlights and used for both audit and educational purposes. Applies to both personal use by individuals, or by groups for things like certifications.

See comment below. Also:

  • Site management and writing could use a "queue" - as specified in the BCC notes - that helps to manage loose book pages for weaving into books. Writing those pages is an "author" job. "Cataloging" those pages, weaving them into the "story" is an editorial job. This same type of task occurs for things like outside references. The web pages are filled with "links." to things. The links need semantic encoding applied and "cataloging" as AIR relationships. This is a "weaving" process that weaves elements like W3C specifications and Wikipedia articles as part of a "knowledge" set.
    • This is why Wikipedia is an excellent and necessary open catalog of ideas, an online encyclopedia. But it operates at a different level and function than AIR or EATS. DBPedia comes closer. But still not there. Both are useful as components of the EATS knowledgebase, accessed "in place." We don't need to, or want to replicate. We just want to index, tag, classify, and "point" to their component elements.
    • Brute force might do that as an incremental, "en masse" task. By scanning our content, identifying links without semantics, which happen to point to Wikipedia, putting them on a tickler, and then working that tickler, we get a much better quality of work accomplished, prioritized for the articles that matter to us. (Some day, if it matters, we'll catalog the whole thing.)


Submitted by joe.vansteen on

This type of thing could be accomplished as a high school, community college or technical program pro-bono volunteer development effort, a version of a hack-a-thon. If we are going to teach systems development, why not teach it on a real, live, open source, development effort. It can be a competitive training exercise. At the end, integrate the amalgamated best-of-breed solution(s).

There are lots of avenues for getting EATS developed and the code maintained over time. It could be a joint program across multiple organizations The key to coordination is architecture management as the system evolves. This can come from mentors and guides that have experiences and insights from both private/public industry and educational institutions, The system will. just like Linux, Java, XML, etc., define a consistent, current (if updated and maintained) open source utility that can be actively and dynamically used as its own training and development facility for use by future generations of users. (Somebody has to do it. Think Scotty on the Enterprise.)

The sling-shot benefits of this have the potential of behaving like the gravity assist on a Juno Earth Flyby. EATS and Architected Futures, or something like this, becoming embedded into core education programs teaching architectural management, systems thinking, augmented intelligence; and using these things as tools across the population; sling shots the planet's population into being able to deal with real upcoming issues like crashing into some form of space junk. That stuff is not all speculation folks. It's statistics. It's likely to happen. We need a plan for when it does. It could happen sooner rather than later. Latest news I saw was that it was "overdue." But so is the California earthquake, also not a laughing matter. We need to plan for these eventualities, and climate change, and a lot of things, collectively.

You may notice that I talk about using EATS or Architected Futures as a global tool by 7.5 billion people, and some of you think, whoa! This kid (old man) thinks he just needs to put a progarm on the App Store and he can be do ... be ... some kind of "King of the World." Like Leanardo Di Caprio in that movie thing, about that ship. No. But I always have a mental sizing in the back of my mind about what maximum capacity might be, and some concept of whether I could scale to get there. In this case, I think yes, so, it's not an issue of concern. Concern right now is more economic efficiency at low usage levels, but that has solutions too, including amortization of costs across a population of users, and being able to right-size the hardware. I can run on a Pi, or Pi cluster, I think. So, a few people in a village in a third world country should also be okay as a user community. The software will be free, as in beer. I like that range.of scalability. It gives me peace of mind as an architect to focus on other concerns.

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.