Typically our stories’ Acceptance Criteria depart like so:

As a user, I want to ...

This is well enough for conveying the intent of the feature to be developed amongst human readers who understand the implications and make inferences about what doing the right thing might look like but in many cases, the existing product already has some pattern of interaction to recreate for novel cases. However, the problem concerns what kind of user is at play: is it a human or is it a machine reading the interface of the application? And furthermore, can we automate the user’s interaction…

If language is generative of communication and learning, what tools would condition the possibility or capability unique to language using living beings? Would it be that non-being confounds the enablement and realization of linguistic machining, languaging and the rest, categorized and classified as productivity, inference, representation and compositionality? Social animals often fail to express these properties even at the level of social praxis (praxeonomics), typically fashioning tools for individual, but not social use beyond mere triviality.

Since the advent of the conceptual scheme, academics and students have engaged in modes of discourse that divide along the distinction of the empirical…

Speaking from Kittler’s point[0], “information hiding” has become a principle of Good Language design; i.e. “encapsulation”, surviving the criticism railed against object-oriented languages (polymorphism and classical inheritance, too, are terrible ideas; but whatever, if an organization or client wants, then the customer gets). So this mentality is the basis from which I make these suggestions. “Hiding” things has become the rule of the day, and I don’t like that; if anything, I want to expose more of the “bare metal” of the underlying systems in the OSI model’s base layer, the Physical layer, to the developers as much as the…

A reply to: https://www.academia.edu/s/6c35647205

As a philosopher, one has an obligation to (a) undermine the pervasive “technocratic delirium”, chauvinism, if you will, that plagues our world-thought and to (b) proclaim that we do *not* entirely belong to the world of objects of which designers[0] are seemly staunchly concerned to assimilate into; indeed, the philosopher’s goal is to remind us of the sacred, or in plainer terms: of what we already know, the questions our ancestors forgot to ask, of the fragility that subtends the sacred which is not nothing but other than experience, or what’s more: the expression, of its…

“The public has no history and no future, the public lives in a golden moment created by a credit system which binds them ineluctably to a web of illusions that is never critiqued.” (Terence McKenna)

We’ve stumbled into a restless web. It lacks the properties of

• Universality (Tim Berners-Lee) and Accessibility
• Durability (Gregory Bateson: A Recursive Vision)
• Convertibility (Pierre Klossowski)
• Priority (Transcendental “in-itself” or function, inclusion, radical presentation of history)

or elsewhere rendered as “CAP theorem” or Karpman’s triangle, and so on but so therefore lacks specification in describing the conditions for the possibility of, Mike Amundsen writes:

• Safety GET…

• Immutability, Composition of Representation (Fodor, cognition and systematicity), Attribute Mental Model, Openness to experience
• Safety (Amundsen/Lamport), Liveness (Lamport; SAM), Fairness (Lamport), Productivity (Fodor), Capability Mental Model, Agreeableness
• Idempotence, Systematicity of Representation, Relationship Mental Model, Conscientiousness
• Presentation, Transclusion, Systematicity of Inference, Neuroticism
• Space-time, Extraversion
• Honor-Dignity (Fourthness, C.S. Hermann)
• Honesty-Humility
• Gossip-sharing and Truth-finding, mutual respect, cosmopolitanism
• Abandon CAP theorem, embrace CALM conjecture (using abstractions like Guesses, Apologies and Memories): Coordination-free, Identification-free, Scale-free, Confluent composition
• Scale cube (Art of scalability: Y-axis, Y-axis, Z-axis scaling)
• Language security, formal input specification languages, full input recognition, Context-free grammars, Turing-complete power and Winograd Schema Challenges
• Computational aesthetics…

As a media type developer, we typically are mildly bemused by some questions of whether the “front end” and the “backend” should exist in the same code repository. In truth, the entire distinction between front end and backend is a bit curious in and of itself, since developers tend to share code styles, patterns and anti-patterns as well as norms and values about what counts as “good” or “performant” or “relevant” or “clever” code.

Generally, it’s just a bunch of nodes talking to each other. Computers do not know they are “front ends” or “backends”, this must be stated in…

I’ve just been reviewing some alternative concept map visual forms for my original diagram created for Domain-driven Hypermedia-oriented Design. Oh, and it’s been updated:

Think of them as metaphors, conduit metaphors, through which to frame thinking terms for talking about the concept map. Some look like train station maps, some look like apartment buildings turned on their side. Others seem to suggest build in this direction (like the “bullet” looking one: reading from the domain-first toward the resolution right-to-left, the direction the bullet points; so maybe flip it around? ¯\_(ツ)_/¯), or “chronologically”. Of course the tabular one is very nice to reason and plan about and through.

Bullet