YAFZ
I think it's a little risky to transfer concepts from one domain to another, without taking into account the working assumptions and the surrounding context. For example something as fundamental as the definition of the concept of 'Black Swan' à la Taleb, is a tricky one, let alone its application to the world of software development. Maybe the best we can do so far is to take this in a very broad sense, and interpret it as a general principle: "first, avoid ruin". But, almost by definition, the events outside the control of a software development/project team can be so extreme that it might render the practical application of the principle almost meaningless. (Think about it: what does it really mean in the context of creating a software product really?)
There are of course meaningful principles that apply to creating investment portfolios, strategies, etc.; do they really apply to software development? Are we using similar data sets and statistics for software development and combination of financial instruments? Can we? That's something I can't say "yes" immediately.
There's also open source TTS from Mozilla: https://github.com/mozilla/TTS
Kano Model and How Do We Disappoint Users While Being Agile
Workplace Communication – Spectrum Between Necessary Exchange and Utter Noise
Fear and Loathing in Lock-Free Programming
Agile Principles Work, Until They Don't
Why LINQ (well, C#) is Broken
When the Scala compiler doesn't help
Formal Methods in Practice: Using TLA+ at ESpark Learning
Distributed Computing: A Haskell How-To
Introducing Knet8: Beginning Deep Learning with 100 Lines of Julia
I wished GNU Emacs had
Disadvantages of purely functional programming
Benchmarking Streaming Computation Engines at Yahoo
On sufficiently smart compilers
Is this the State of the Art for grammar checking on Linux in 21st century?
Coding challenge: partial results semantics
Machine learning in 10 pictures
Scala versus Python and R: software archaeology in bioinformatics
How to use extractors in Scala for powerful pattern matching – Devoxx style
Capitalist Science
CUBIST: Explore and visually analyze relations, dependencies, and clusters
Java 8, Lambda Expressions and the Psychology of the Masters of the Universe
My point is not to denigrate any popular process or advanced technological tools. And I don't embrace big design up front for everything, especially when it makes it even more easier (and more expensive) to paint yourself into a corner. I wanted to draw attention to a simple fact: sometimes the medium of production is not necessarily the best medium for thinking about that production and being immersed in that medium can prevent you from realizing this, thanks to the human psychology that took hundreds of thousands of years.