Live data from Hacker News

A Proposal for an Antifragile Software Manifesto

sciencedirect.com

11–20 of 46 posts

Re: A Proposal for an Antifragile Software Manifesto

#11
As with any manifesto, words, interpretation, and practice are where they fail. I've been through the Agile/Scrum classes, yeah, great. Does management buy in, despite professing such? Yeah, not so great.

Unfortunately, for me, whenever I see the word "manifesto" in relation to computers, this is the one I immediately remember...

http://phrack.org/issues/7/3.html

Re: A Proposal for an Antifragile Software Manifesto

#12

This will be difficult to do in text (imagine a triangle): Quality Time Cost Right, which one is more important? and more importantly who gets to decide which one is more important?

The triangle is "cheap", "fast", and "highly available".

Pick any two...

Re: A Proposal for an Antifragile Software Manifesto

#13

Earlier quoted context omitted.

Honestly, I would love it if anyone could make the decision at all. Usually it's "I want all three".

Yep, managers seem to think the triangle can be overcome with enough money/prowess/brute force.

Money in many cases can buy you (some) time.

Re: A Proposal for an Antifragile Software Manifesto

#14

Earlier quoted context omitted.

Honestly, I would love it if anyone could make the decision at all. Usually it's "I want all three".

Yep, managers seem to think the triangle can be overcome with enough money/prowess/brute force.

Well, if they're willing to invest money, then they've chosen, no? Cost is not important, but timeliness and quality are.

Re: A Proposal for an Antifragile Software Manifesto

#16
Antifragile refers to a property in which a system does not just resist breaking down under disorder and stressors (robust), but gains/learns/becomes stronger. A good example is how bones heal back stronger where they were broken.

While we are currently able to build self-healing systems of a sort, fault-tolerant Erlang systems being a good example, it doesn't seem we can build systems that are truly antifragile on their own, that would require strong AI. Otherwise, humans monitoring and intervention are required to improve systems under duress.

This manifesto does include "team" and "organization" to account for that, but a true autonomous antifragile system is a ways off.

Re: A Proposal for an Antifragile Software Manifesto

#17

Antifragile refers to a property in which a system does not just resist breaking down under disorder and stressors (robust), but gains/learns/becomes stronger. A good example is how bones heal back stronger where they were broken. While we are currently able to build self-healing systems of a sort, fault-tolerant Erlang systems being a good example, it doesn't seem we can build systems that are truly antifragile on t…

Software such as fail2ban that bans harmful IPs and spam filters that learn over time would qualify as antifragile. I can't think of anything at the system security level.

Re: A Proposal for an Antifragile Software Manifesto

#19

This will be difficult to do in text (imagine a triangle): Quality Time Cost Right, which one is more important? and more importantly who gets to decide which one is more important?

You can have all three. Prioritizing quality from the start, by doing design reviews, pair programming, tdd and so on, will actually reduce time needed to deliver fully functional software, and therefore lower overall cost.

Re: A Proposal for an Antifragile Software Manifesto

#20

As with any manifesto, words, interpretation, and practice are where they fail. I've been through the Agile/Scrum classes, yeah, great. Does management buy in, despite professing such? Yeah, not so great. Unfortunately, for me, whenever I see the word "manifesto" in relation to computers, this is the one I immediately remember... http://phrack.org/issues/7/3.html

And this is the one I remember instead:

http://programming-motherfucker.com

Post reply on HN