› Antifragility in WordPress, Bootstrap, and Grunt

Reducing Downside / Maximizing Upside (Under Construction)

Websites, software, and tools in general are used to amplify the agency of individuals – these transactions often take the form of money and businesses rendering services across time. Stated in terms of antifragility: the market fluctuates and it is apparent that tools like WordPress, Bootstrap, and Grunt can reduce the time and costs of creating and maintaining websites that fit into many different services, and niches, that individuals exchange resources for. Fragility is evoked by stressors that constitute the volatility of any given system, and to paraphrase from Hayim Makabee: the main source of volatility in software are functional changes (new requirements on functionality), although non-functional changes (ie. refactoring) provide volatility as well.
(https://effectivesoftwaredesign.com/2014/05/25/antifragile-software-design-abstraction-and-the-barbell-strategy/)

Clearly, one would rather their chosen systems of use to be robust, as opposed to fragile, so they continue transforming chaos into additional agency. Taleb established a third class that has come under heavy consideration for modelling uses, it extends, in explicit scientific terms, the notion that systems can be designed to not only withstand but benefit from chaos.

Taleb’s fragility spectra is something like:
0 Fragile – Destroyed easily by volatility
1 Robust – Immune to volatility
2 Antifragile – Benefits from volatility

Antifragility vs Other (Meta) Measures – Agency, Antifragility, Material Gain:
Are these all different definition sets restating the same functions with different focuses? Are they refined restatements of coding principles, like parsimony and modularity?
0 Antifragility – > Chaos relations for systems
1 Agency – > Full Accounting for systems
2 Material Gain – > Concrete measures

Measuring of and decidability for antifragility – metric 1 : Barbell

“What do we mean by barbell? The barbell (a bar with weights on both ends that weight lifters use) is meant to illustrate the idea of a combination of extremes kept separate, with avoidance of the middle … Let us use an example from vulgar finance, where it is easiest to explain, but misunderstood the most. If you put 90 percent of your funds in boring cash (assuming you are protected from inflation) or something called a “numeraire repository of value,” and 10 percent in very risky, maximally risky, securities, you cannot possibly lose more than 10 percent, while you are exposed to massive upside. Someone with 100 percent in so-called “medium” risk securities has a risk of total ruin from the miscomputation of risks. This barbell technique remedies the problem that risks of rare events are incomputable and fragile to estimation error; here the financial barbell has a maximum known loss.” – Nassim Taleb, Antifragile

The idea being that any system is ideally first reinforced against easy destruction, and next optimized to take advantage of good risks. Makabee notes that systems are more robust through abstraction, he lists information hiding/encapsulation, the open-closed principle, and inheritance heirarchies/framework as examples:

“Now that we have identified the sources of volatility (changes) the question is: What is the software equivalent of a Barbell Strategy?

The answer is: Abstraction. Software systems should have a structure and organization based on different levels of abstraction. In this case the duality of the Barbell Strategy is expressed as the separation between high-level abstract elements and concrete implementation details.

Abstract elements: Are robust, and should not be easily affected by changes.
Concrete implementation details: Are fragile, directly affected by changes.

In other words, software systems should be built in such a way that the volatility (changes) does not affect its structure and organization, preserving the main, high-level abstractions and requiring modifications only on the low-level, concrete implementation details.”

WORDPRESS LAYERS OF ABSTRACTION CORE AND TEMPLATES

0 Users Concept of Content (dictates core software to use)
1 WP Core concept
2 WP Core implementation
3 Theme concept
4 Theme implementation
5 Plugin concepts
6 Final Content (updated most often)

Again, the open closed tactic is employed (one can expand easily on the core to avail one’s self of change, although the core itself is relatively closed to change). The further to the base (0) of the spectra the more closed and stable that level of abstraction is. The concepts of the functions WP Core must perform change less than the Core itself changes.

One main use of stability is to reduce overall vulnurbility to risk. One use of reduced vulnurbility is to take the opportunity to make intelligent risks (perhaps many small risks, with potentially high rewards). Now, because WordPress is deployed over so much of the internet, it is potentially a larger target for hackers, yet subjecting the same core to such varied attacks while also subjecting it to the demands multiplied across the less stable, more varied add ons.

The parts of WordPress that change, allow it to adapt to many situations at small cost, even if said situations are temporary. This is because the full force of the WP Core is brought to bear on many tasks through alterations in more disposable less expensive elements such as themes, contents, and plugins.
For further consideration: theme templates, what other frameworks are very popular or functional? Why? How?

CSS AND Bootstrap
Same as WP: Core remains same, applies to many different tasks.
Different from WP:

GRUNT WORKFLOW
Same as WP: Core remains same, applies to many different tasks.
Different from WP:

GULP WORKFLOW
-coming soon-

TEMPLATES, AGILE, AND DRY DEVELOPMENT
Many of the concepts for antifragility actually extend and fit in with the concepts of agile and dry development. [expand this]

Measuring of and decidability for antifragility – metric 2 : Parsimony
Corollary in software:
Corollary in agency:
Corollary in material gain:

Measuring of and decidability for antifragility – metric 3 : Stoicism
Corollary in software:
Corollary in agency:
Corollary in material gain:

Iterate across more principles

FROM ROBUST TO ANTIFRAGILE (move to top?)
Antifragility is about reducing vulnurbility downsides (creating robustness) and opening up as many opportunities to “catch” good luck as possible. The idea being that hard work means moderate success but for improbable levels of success all we can do is craft our lives to to maximize those positive potentialities. Supposedly Taleb’s example of this was buying many “penny stocks.”

More on microservices and scalability https://www.infoq.com/articles/microservices-intro

Repost: OpenShift V3 Deep Dive – The Next Generation of PaaS w/ Docker