Architected Futures™

Tools and strategies ... for boiling the ocean

About Joe


I'm a "retired" enterprise application systems architect (software engineer) with interests in astronomy, cosmology, astrology, photography, religion, politics, science, systems and complex problem solving. I don't tend to believe in absolutes (everything is relative). I enjoy problems with multiple correct answers, and those with no correct answers. I enjoy metaphors, science fiction, dystopian novels, historical fiction, mystery, philosophical intrigue and walking in Tilden Park with my dog Leo (He's a lot older now). I spent 35 years at Bank of America (the California-based institution) as a priest and then high-priest of IT witchcraft. I alchemized the customer facing retail software blending between EATS and WEST in the merger  between BofA and NationsBank.  Now, I have the good fortune to select and tackle the problems I always wanted to, and in the way I thought they should have been approached before.  As I write this it's 2021, and I satrted at BofA in January of 1970, so that's 50+ years of Info Tech.

I have 15 years of new "Architected Futures" IP, which is a regurgitation and refinement of my work as an IT architect for Bank of America over a 35 year period. The second portion of the 35 year period was a regurgitation and refinement of the 1st potion, but for the reverse target audience and marketplace.  Basically I did 35 years at BofA, 17.5 on each side of a divide, macro and micro financial flows.  I was also responsible, in my time, for the interchange between the flows, and the interchange book-keeping involving Bank portfolio investments, Cashiering, World Banking Money Flows and Currency Exchange, etc. I authored architectuire documents for things called STACS (Securities Trading and Custody System) and GCMTAD (Global Capital Markets Trading and Delivery), along with others; after architecting and implementing Customer Safekeeping (CSK) and Securities Investments Control (SIC) systems for the Bank Investment Securities Division. I've directed minicomputer performance evaluation tests to have manufacturer engineers certify to design defects in "theoretic" operations. (READQ and the GA/440) I've worked with SRI to develop and demonstrate models for anticipatory modeling of forecated needs. (STACS) I've conducted DELPHI studies to hone forecasting projections (STACS) to the point where the estimate killed the project. ( $mm / 5 yr). It was replaced with READQ / 5 yr. [Reread this paragraph if you have a hard time understanding where this all went.]  

In college (in the late '60's), my original goal and training was to become an architect, of the buildings and cities variety; but I discovered that was not my talent. Instead I gravitated toward management science and Operations Research and discovered computers, which resulted in a career in IT. During my paid career in "systems" I found that I've bumped into and sought guidance from a series of systems thinkers (Ackoff [Paper in Systems Analysis Techniques], Forrester [Books and papers on DYNAMO], Weinberg [Class at Ethnotech in Lincoln, NB; Are Your Ligts On? Weinberg&Weinberg, etc.] and others), but I didn't understand or appreciate the "field" of systems thinking which was unfolding/developing co-temporaneously.  Instead, I was focused on the application, the use, of systems thinking toward business automation. Specificall financial data flows.  I'm an architectuiral engineer, not a scientist [theoritician]; but now, I have the opportunity to do "catch up". And fill-in interpolation to: "What makes engineering work?"; and, "What do you do {architect} with science, that people find useful?"; and, "How do you utilize science toward peoples best utility?".

I'm a futurist and a Futurist.  I have been since reading Willy Lea and seeing and experiencing Project Vandenberg, watching misilles rise and explode, on the launch pad, on TV, in the 1950's.  And, I remember reading similar but different narratives from Ayn Rand; and other on other tracks.  I believe in the concept of an "architected" future - one which is, or should be, consciously planned for; one that is both intentional and, in some "Zen" sense, "accepted;" as opposed to simply being allowed to unfold as a result of chaotic forces ["Chaordic" is my correct term, coined by Dee Hock of VISA.  The space which blends CHAOS and ORDER. It's the "peace" at the center of a hurricane. v5.2021.0522-jvs].  I don't believe we can specify an exact course and target, but I think we can influence trajectory and hopefully steer around or mitigate impending problems. I believe in "ideals" and using them as compass points which are technically navigable targets.

My background and expertise is in what I am beginning to understand as "hard" rather than "soft" systems, but I have always sought an understanding and approach to technology as a hard component within a "soft" human social context. What I'm finally configuring as EATSv5 is a multi-dimensional Sanwich Model.  In software engineering jargon terms, a PAC Stack. Context is extremely important. My current passion is directed toward the development of a tool-suite which assists with applying that mindset toward hard, soft, routine, extreme, and wicked systems problems. From my perspective, you can never total solve a problem. So, maybe I'm cheating with my algorithm.  All you can ever do is trade in one set of problems for another. I don't know that you can truly solve natural problems.  But you can fix man made fuck-ups and you can exchange one set of natural problems for another set that are less troublesome. Bugs in technocal design can be fixed. The sooner they can be identified, and acknowledged, the less expensive and more satisfying the solution. Hurt radiates. Wellness radiates. Wellness beats hurt all to hell if it's pleasurable enough. (Sex traffic drives wide-band expansion.)

I enjoy living surrounded by my 7 Redwood trees, in my Berkeley terrerium, with my loving, artist wife Hallie. I have favoritism toward softer reds and a variety of CA white wines, Kaluha, medium rare grilled hamburgers and Trader Joe's raisin bread with peanut butter. I want to die an engaged old man with plenty left to do on my bucket list, and I want to spend as much of that future journey in the enjoyment of family and friends, especially Mason. This web site is dedicated to all of the people with whom I've interacted in a significant manner, and for Mason, who functions as my personal avatar toward a hopeful future.  Everyone has their own mix of people and ways to pass things forward. EATSv5 will be mine.  Search for "Mason" and look for "Mason's World".  Zoom in and Out. Today it's hard content with understanding and navigation to get around. This is HTML using HTTP[S].  

For anyone reading: look at the dates on the pages [other than this one].  If you want to know what's coming, you have to know what's here. I'm tired of re-writing because other people want to find new and better ways to do old things.  More than one can play a game, and it takes two to tango.  The question is, what happens with 3, 4, 5 and what forms do progressions take? AND, which progressions take which forms; because they're all patterns on relationships. 

Personal Perspectives

I have a place on this web site, some times I forget where stuff is, but it's the legal stuff, at the bottom of every page. that talks about disclosures. What is doesn't say that needs to be said somewhere is that this is one person's opinion about a lot of stuff. Most of it, and I need to be corrected when this isn't the case, is factual, and logical, and based on common sense and reasoning. It's engineered. And, according to what I know, it's reasonably good engineering. (Help me identify bugs so we can correct them, because I'm implying that everyone in the world can find useful information here, not crap that's going to send them in the wrong direction, mislead them for someone else's gain, any any other traps.  That's a "disclosure" statement.) I rely on other peoples information, and other people's logic and analysis, and the education and training that I received from Jesuits and from the State of California. (More disclosures.) I try to verify before I publish, as best I can. The hard engineering presented on the site should be unbiased, as much as possible, and you should be able to independently verify stuff if you want to take the time to do that effort.

I DID NOT GET PAID FOR THIS, although I suspect it will make me some money. But you're getting it for free, so, caveat emptor. My hope is that in your judgment it will be free as in priceless, as in the MC commercials; not free as in worthless. But, it's your evaluation. (Evaluations solicited.)

My point here is that as much as I try to be unbiased, and neutral from an engineering "clean room" sense, there is no way that I can completely do that, because I'm one of you, and I'm human, and I have a particular context, called "me," that I live in, and that affects how I do things, and how I think. I can't be completely unbiased, just like the best quality of the evening news, but we can try as much as possible to label what we feel may be prejudices within our views as we express them. You will find "quips" throughout the content of this web site, and, until some other people blog or write documentation here, they are all mine. They, and the "facts," form my personal perspective and you should keep that in mind as you travel the site content.

Can anything along the lines of what's being talked about here actually be done? I think so, that's my honest opinion. But, it's a personal perspective.

Other material on the site is the beginning of project planning and documentation on how to get it done, also from my perspective. The values and principles below are more disclosure. If you want to debate them, cool. If you want to argue about whether they should be flipped in positive/negative polar alignment, you are wasting both of our time and you are on the wrong web site. It might be interesting and useful, purely as a philosophical debate, but that's not how I want to spend my time.

I would like to see an extended set of these value and principles concepts debated and adopted by the members of an interested group ( a COI as I've described them here). These generalized concepts: Principles, Values, and others like them, are what the framework described on this site uses to evaluate its own effectiveness, as a tool, for accomplishing its goal: that humans, as one known version of a stellar tribal population, should live long and prosper.

It's my alternative to writing an anti-Ayn Rand novel in a sci-fi genre. Or, maybe it would be a supportive novel1; in either case, subjectivity and relativism is what we will always be forced to live with, in my stories, while being as objective as possible.

Values and Polarities

These tend to be "scales" with more of one, less of the other; this direction / that direction; Yin/Yang type things.

  • The whole is more important than any individual part
  • Ends do not justify means, means are a method to accomplish ends
  • Cooperation beats competition in system efficiency and effectiveness, but competition is useful in alternatives analysis, quality testing and fostering innovation among diverse competitive elements
  • Extremism is not a good form of politics. In fact, (opinion) it's a very bad form of politics. They Hatfields and McCoys used to be a side show for entertainment. Almost a joke. Now, they run one or more of the top legislative bodies in the world.


These are guiding concepts

  • People are the coolest thing this planet has got, they are also their own worst enemy. They can screw up a good thing in no time if they play with toys in a chaotic manner. The bigger the toy, the bigger the boy, the bigger the issue. People need regulation too.
  • Problem management needs to start with a "right sized" understanding of "What is the problem?" Demanding immediate solutions before you've identified the problem, is a problem in itself (See: Pg 7, "Are Your Lights On?"). Right sizing is context sensitive.
  • Understanding and awareness of urgency and criticality are crucial to survival. Don't ignore the obvious because it's counter to what you wanted to believe. Face facts!
  • When solving triage problems, optimize toward solution patterns that minimize future constraints and maximize future opportunities. When solving strategic problems, optimize for alignment with the environment. 
  • Rouge elements can be managed via atrophy if core issues that feed them can be addressed in a "right sized" manner, thus starving them for lack of supply (a military tactic that might take awhile for some stuff) Expect this to come up forever as we move into the future. Stuff happens.
  • Never, ever lie to yourself. Know (or find out) where "truth" lies, and its confidence limits. Figure it out, choose and act before things get critical, the longer false assumptions and bugs remain in the system, the harder they are to eradicate and correct for, and the more damaging and expensive the repairs. What could have been routine maintenance becomes a complete overhaul and replace operation.
  • Harmony is grease for making progress. Respect everyone's contributions to common goals, no matter how esoteric. Ego-based diruption of harmony is NOT a contribution. Extremism  as a pathway to anything is not a virtue, it's called being an outlier; get over it.
  • a growing list, to be embedded on a better profile page at some point.

Claim to Fame

  1. My first computer program was written for a Litton Monrobot IX, and I was once the proud owner of not one but two Cromemco® S100 microcomputers.2
  2. I once took a course in the 1970s at Ethnotech from Jerry Weinberg. I remember a number of things from back then, and still have my "Are Your Lights On?" book, and others. That was a really cool week. I was there when ... 

View Joe Van Steen's LinkedIn profileView Joe Van Steen's profile, View Joe Van Steen's brain

  • 1. An Ayn Rand Interest Group could be interesting. I could do both sides of that. And writing a science-based future fiction novel was something I once wanted to do. An Arthur C. Clarke kind of thing.
  • 2. My first personal computer was a Cromemco® Z2-D. (The "D" meant it was a "Z2" that also include a disk(ette) drive!) Later I added a Cromemco® System-3. The Z2-D was a 64K machine running CDOS (based on Digital Research DOS, a predecessor to MS/DOS) and sporting two single-side, single-density 5.25" floppy disks. The System-3 was a banked switched 128K machine running Cromix and sporting two 8" floppies! Go here for a little more on what these machines were all about.