Speed, Agility, Resilience
Trusted Experts in Microservices, Cloud Native & Chaos Engineering
  • Home
  • EBooks
  • Contact Us
  • Consultancy
    • One-to-One Online Consultancy
    • Onsite Consultancy
  • Training
    • One-to-One Online Training
    • Building Reliable Systems
    • Building Antifragile Systems with Microservices Course
    • Fast Track to Cloud Native Java
    • Fast Track to Applying DDD for Effective Microservices
    • Fast Track to Running Production Microservices
    • Fast Track to Chaos Engineering
    • Autumn of Cloud Native
  • Speaking
    • Schedule
    • Slides and Videos
    • Brown Bag Events
  • Blog
  • FAQ
  • Client Feedback
  • Gallery
  • (Print) Books
  • Essais

Why don’t people design antifragile software already?

3/3/2014

0 Comments

 

The first and most obvious reason is that it takes effort. Much like simplicity, antifragility requires recognition and to be valued in order for it to be applied. Otherwise any antifragility is serendipitous at best.

Antifragile falls at the other end of the spectrum from fragile, with 'robust' the mid-point of the triad. Fragile software is evident in every decision to abandon a legacy codebase as it's fragility prevents it adapting to new needs. Robust software is often high quality for yesterday's problems and will withstand some change, but will often end up resisting your change when you really need it. All the best techniques of the craftsman often lead to this high quality but resistant to change software.

Antifragile software has been designed, architected and is delivered in such a way as to thrive on change. Change here, even the unexpected, is seen as an advantage.

After looking carefully over my recent and past software products, fragile design hurt me, robust design meant someone had to be upset, but antifragile design, architecture and delivery process delivered satisfaction to all quarters.

The fact is that people do occasionally deliver antifragile software. You only have to look to companies that are innovating at pace with their software products, and often with few people, to see antifragility in action.

The first step to getting these gains is to understand and value antifragility.

For more information on Antifragility generally, the canonical book by Nassim Nicholas Taleb is the place to start.

For more on Antifragility in Software, that's what 
my book is all about and I expect to have a complete draft ready this week. If you can spare 3 days in London to learn about how to develop and evolve software faster than the competition, then my course at Skills Matter would be time well spent.

For help adopting antifragility in your own software, contact my team at 
Simplicity Itself.

0 Comments



Leave a Reply.

    Musings on software development

    Archives

    September 2017
    June 2017
    November 2016
    September 2016
    May 2016
    February 2016
    September 2015
    August 2015
    June 2015
    March 2015
    January 2015
    December 2014
    November 2014
    October 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    December 2013
    August 2013

    Categories

    All
    Announcements
    Antifragile
    Books
    Innovation
    Life Preserver
    Microservices
    Philosophy
    Psychology
    Reviews
    Software

    RSS Feed

Products

EBooks
​(Print) Books
Consultancy
Training
​
Speaking

Company

Essais
FAQ
Client feedback
Gallery

Support

Contact
Picture
© COPYRIGHT 2018. ALL RIGHTS RESERVED.


Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.