Or “Development”? Whatever a developer chooses to take from this post, it may be applied to development per se, in some areas, just a little? Who’s to say? It’s a well-charted territory: Mike Amundsen (BDFL) already has developed and architected many rigorous and swaggerly demonstrations of the much feared “generic web client”, wherein our understanding is brought to discuss the requirements for both a server too. His book Building Hypermedia APIs with HTML5 and Node kickstarted a campaign, really, of a general style and focus of writing software that is explicit, scientific, testable, highly evolvable and modular: but hypermedia-oriented. Of course, the “first issues” of his “api-starter” repository might be to add Yeoman templates. What might they look like, for Data (fixtures, mocks, etc. directory under “support” in DDD) or Resources (are these not “apps” in DDD?)? What reasons might we have for choosing this configuration over that in our template patterns: is it to produce “pages”, web page elements, native app components, content-management system paradigms have many “widget” and “structural” representational Data Types (message models?); — does it, the response, need schema.org …
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 verification of the effectiveness of learning styles. Should we wonder if programming styles are grounded in the same or similar ensemble of abstractions and representations, or patterns of recognition which would resolve in epistemic justifications that are networked information? Of course the credibility of lateral thinking and the non-standard model become those bases of cognitivity for which an educator or educologist is in want of principles to determine the spatiotemporal interlocking with the language-object as a meaning-tag engenders the information necessary for empirically-friendly development, description, interpretation and explanation of hypotheses. Should theories and conjectures gain competitive ground or establish ontological commitment across all modes of discourse, the application of Segmented Discourse Representation Theory (SDRT) suggests a tenable mapping between rhetorical relations and sensible relations (Contingent Computation. Beatrice M. …
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 users, but obviously in a way that is intuitive, meaningful, etc. toward better shared understanding of these systems. …
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 totality without totalization. …
“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
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:
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 the request-response volley of messages. One says GET
the other has some Accept
headers, and on so, but in truth at any time a server can become a client, depending on the goal that we has humans have set before us, whether it is to decentralize an economy or simply serve up a web page with a picture of a kitten on it. …
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.
link dump. that’s it
extended here
the web fundamentally is a distributed hypermedia application
developers may wish to use ionic v4 (v1.3.3?, but install ionic@4
, etc.).
figure 1:
Philosophy has amply supplied us with tools and technology which can be deployed in a performance of composition such that their value as output can develop, describe, explain and interpret variable input domains within a knowledge graph. Take “what is it like to be a(n) X” by Nagel, coupled with Quine’s “to be is to be the value of a variable”. By simple substitution we derive “what is it like to be the value of a variable?” It’s a naive gesture, as if partaking at a fine dining restaurant and placing a salad fork in a rib eye. But is Nagel’s question even originally conceptually hygienic for any X? For some things it may seem as profound as uttering that “the sky has the blues”. What is the analytical value of such talk? Is it reducing hard-working philosophers’ corpus to quotations, half-baked paraphrases, etc.? Perhaps, one can only hope. Philosophers like comedians (Jerry Seinfield, at any rate), want people to be talking like them in how things are going. That’s really the testament of any philosopher’s true wealth: the frequency with which their conceptual machinery is presented in our contemporaries’ philosophical activity. …
About