This is spot on in my experience.
As I grow in my career as a software engineer, it's funny how much more often I notice that the things that set one apart in the field is a level-headed understanding of the fundamentals and a calm resolve to take into consideration what's worked in the past, much more than one's ability to "chase the shiny".
Honorable mention of the Lindy Effect [1] here - one of my favorite ideas from Antifragile [2].
[1] https://en.wikipedia.org/wiki/Lindy_effect [2] https://www.amazon.com/Antifragile-Things-That-Disorder-Ince...
Taleb - ttps://en.wikipedia.org/wiki/Nassim_Nicholas_Taleb Antifragile - https://www.amazon.com/Antifragile-Things-That-Disorder-Ince...
Basically all current investments are high-risk in the age we live in, because we are "at the brink of the chasm" on all fronts:
- general technology: ...the barriers to market are so low that a startup can spring to being at any moment and eat all your profits away
- (social) media / communication: anything can change anytime, today's Facebook can be tomorrow's Hi5
- biotech: we're getting closer to the "you can do it your garage stage" which will change everything
- world politics: India and China are big players now and their moves can no longer be predicted, also US internal politics is a cauldron of volatility, and in a decade or two we'll have the "New Africa" rising... good luck predicting anything
- ML/AI: we might be at the brink of f Singularity with superhuman-AI around the corner... but we have no idea whether it will be in 5 years or 100 years (!) ...this alone is enough to fuck up all worldwide future prediction on anything... when you're staring up from somewhere around the foot of an exponential curve everything looks like "wtf, nothing makes sense"
And also, the last economic "crisis" increased everyone's aversion to risk, kind of the opposite of what you'd need now to increase level of investment...
What needs to change is the attitude of people with money towards risk! I'd love to see people like Elon Musk succeed long-term, not because I like them or what they are doing, but because they are the only ones with an attitude that can create growth right now.
We should really re-learn thinking and working with volatility, maybe starting from what Nassim Taleb says in his Antifragile (https://www.amazon.com/Antifragile-Things-That-Disorder-Ince...) and his talks like How to Live in a World we Don't Understand (https://www.youtube.com/watch?v=iEnmjMgP_Jo - warning: he's a terrible speaker... and not a great writer either, so getting to the root of his ideas will take time). Maybe not. But current "risk reduction" attitude cannot work (hint why: even if you reduce Infinity by 20% you still have f Infinity!).
Antifragile https://www.amazon.com/Antifragile-Things-That-Disorder-Ince...
High Output Management https://www.amazon.com/High-Output-Management-Andrew-Grove/d...
The Master Switch https://www.amazon.com/Master-Switch-Rise-Information-Empire...
Thinking Fast and Slow https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp...
As it grows, I'm sure inertia will continue to slow it down, but that willingness for reinvention seems like quite a powerful property.
(Another current book – Antifragile (http://amzn.to/2nr15ST) – discusses systems that benefit from randomness and volatility. I wonder if the willingness for reinvention allows for a kind of anti-fragile generational selection to work: instead of waiting for selective forces to birth a different and new stronger generation, you transform yourself (or your company) to _become_ that new generation, allowing you to directly benefit from selective pressures. It's tough to do, psychologically and culturally, and the willingness to do so seems an extremely valuable quality to cultivate.)
I agree that expecting to create 12 great projects next year is a stretch and odds are that 12/12 will become vaporware, however, the lessons learned and the potential (albeit small) for any one of them to actually become something makes this a worthwhile endeavor to me.
Actually reminds me of something I read from Antifragile[1]:
> Rule 4: Trial and error beats academic knowledge.
> Things that are antifragile love randomness and uncertainty, which also means—crucially—that they can learn from errors. Tinkering by trial and error has traditionally played a larger role than directed science in Western invention and innovation... [2]
Say what you will about NNT's writing style, but the guy makes a lot of sense to me.
[1] https://www.amazon.com/Antifragile-Things-That-Disorder-Ince...
[2] http://www.wsj.com/articles/SB100014241278873247351045781209...
You're right that only signed ints admit undefined behavior. Unfortunately you can't get by using just unsigned ints. So for me the choice was between mixing signed/unsigned and just using signed everywhere. If use of signed ints is unavoidable and also leads to undefined behavior, I'd like to exercise it more often in hopes of learning faster what things I shouldn't be doing. This seems like the more antifragile choice (http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...).
I learned about this concept in http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
* Nassim Nicholas Taleb. Antifragile, things that gain from disorder http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
* Jared Diamond. The World until yesterday, what can we learn from traditional societies http://www.amazon.com/World-Until-Yesterday-Traditional-Soci...
* Frans de Waal. The Bonobo and the Atheist: In Search of Humanism Among the Primates http://www.amazon.com/Bonobo-Atheist-Search-Humanism-Primate...
* John Higgs. The KLF: Chaos, Magic... http://www.amazon.com/KLF-Chaos-Magic-Music-Money-ebook/dp/B...
* Joseph Jaworski. Synchronicity, the inner Path of leadership http://www.amazon.com/Synchronicity-The-Inner-Path-Leadershi...
* Piero Ferrucci. Your Inner Will, finding personal strength in critical times http://www.amazon.com/Your-Inner-Will-Personal-Strength/dp/0...
* William Irvine. A Guide to the good life, the ancient art of stoic joy http://www.amazon.com/Guide-Good-Life-Ancient-Stoic/dp/01953...
* Chogyam Trungpa. Shambhala: The Sacred Path of the Warrior http://www.amazon.com/Shambhala-Sacred-Warrior-Chogyam-Trung...
* Tomas Malik. Patience with God: The Story of Zacchaeus Continuing In Us http://www.amazon.com/Patience-God-Story-Zacchaeus-Continuin...
* Nick Winter. The Motivation Hacker http://www.amazon.com/Motivation-Hacker-Nick-Winter/dp/09892...
* Chas Emerick, Brian Carper, Christophe Grad. Clojure Programming http://www.amazon.com/Clojure-Programming-Chas-Emerick/dp/14...
Fiction:
* Peter Hamilton - The Reality Dysfunction
* Neal Stephenson - Cryptonomicon (his other hit: Snow Crash is surprisingly more history then SF now...)
https://news.ycombinator.com/item?id=8153457
Are we not talking about this because it's not relevant, or because everyone here is so invested in this disruption movement?
TL;DR: Read Nassim Nicolas Taleb, he has a lot to say on the likelihood and impact of highly improbably events (Black Swans)... like the successful of highly innovative products. Everything I say next is a rambling couching of the ideas of this article into his framework with the hope that someone else will engage with it.
Personally, I think the key point is here:
"Companies that were quick to release a new product but not skilled at tinkering have tended to flame out."
Which reminds me of the NNT's barbell approach to mitigating Black Swan's. Invest the majority of your energy conservatively in safe, non-risky ventures and then spread the rest of your energy across high-risk ventures (tinkering) with extremely high (or unlimited) potential upsides.
New technology has allowed the creation of many more Black Swans for businesses through innovation and they can be positive or negative depending on whether you are the disrupting company or the one being disrupted by this new innovation Black Swan.
Established companies that don't tinker, don't expose themselves to positive innovation Black Swans... while startups that ignore all established wisdom gambling on a single Black Swan innovation expose themselves to the reality that 9/10 innovations don't actually result in Black Swan level disruption.
For those that don't know what I'm talking about, I definitely recommend Nassim Nicolas Taleb's The Black Swan and Antifragile:
http://www.amazon.com/The-Black-Swan-Improbable-Fragility-eb...
http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
</rambling>
It's tempting to think, "Ah, people! So terrible at predicting things." I think it's interesting to think about why that is.
The main problem, I think, isn't that people make wrong predictions altogether. It's that it's very hard to see how things will change and evolve over time, and how the ecosystem will change with it. The "One Laptop Per Child" idea [4] sounds a little dated and silly now.
I suppose if we just remember that progress is continuous rather than discrete, and that a lot of seeming limitations can be overcome with currently-unlikely innovations, then a lot of predictions will be forced to be a lot more precise.
Perhaps the Newsweek prediction might've been amended to, "In its present form, the Internet is unlikely to change the world."
The problem with predictions is– things rarely stay in their present forms, and the world around them rarely stays the same, either.
I think pg addresses this in his most recent essay, "What Microsoft is this the Altair Basic of?" [5] In his words– "they practically all seemed lame at first."
So we have to learn to live in a world where our initially valid assessments of a thing might become rapidly invalid because of change. And this is where Nassim Taleb's work about the problem of prediction [6] comes into play. Rather than trying to predict a particular outcome, it makes much more sense to focus on evaluating robustness and antifragility– "How will this thing respond to change? What are the potential upsides, what are the potential downsides? What will kill it? What will give it more utility?"
Even if the odds are really low that something might come around, if the payoff is high enough, it might be worth betting on. I think that's the whole point of things like YC.
___
[1] http://www.newsweek.com/clifford-stoll-why-web-wont-be-nirva...
[2] https://web.archive.org/web/20070116071424/http://www.engadg...
[3] https://news.ycombinator.com/item?id=8863
[4] http://en.wikipedia.org/wiki/One_Laptop_per_Child
[5] http://paulgraham.com/altair.html
[6] http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
Headquarters: Montreal | http://www.omsignal.com
Link to Job Offer: https://github.com/OMsignal/omsignal-job-offers/blob/master/...
OMsignal is made possible by the expertise of Smart Textile experts, Data/Bio Scientists, Hardware, Firmware and Software Engineers. Please note that this offer is mostly focused on Full Stack Engineers, but we are also looking to hire smart Data Scientists who have an interest in biodata and possibly people who could help bridging BLE/MSP firmware and driver development.
What we do
==========
OMsignal is an exciting Montreal start-up developing a revolutionary
line of bio-sensing clothes that connect seamlessly
to smartphones. The company is at the intersection of the wearable
technology, well-being and fashion markets.We are a well-funded startup [1] working to deliver a smart biometric shirt. You can read more about our mission on [2]. And for those who followed the US Open 2014, we are the technology behind Ralph Laurent Polo Tech.
We just shipped the product to our first customers.
What we are looking for
=======================
We are looking for Full Stack Software Engineers who can
help us to architect, design and implement a complex system based
on bleeding edge technologies (Scala, Akka, Spray, Reactive Programming [3],
iOS, Swift, Docker...), a modern architectural
style (Micro Services, CQRS, Event Sourcing, Eventual Consistency),
and a clean codebase (Clean Code, Domain Driven Design…) -- emphasis on
the “Engineer” over the “Full Stack” part.In-depth knowledge of the technologies we use is not required, but having strong Software Engineering foundations is (Algorithmics, Design and Architectural Patterns, …). Understanding that code is read much more often than it is written is an absolute must.
You should be willing to face the upcoming challenges (Machine Learning, Predictive algorithms, Opening the platform/iOS SDK/API, -- who knows the rest?…).
And of course, you need to speak/write english fluently (we need to understand each other, right ?)
The Technologies we currently use
=================================
- Backend : Scala, Akka, Akka Persistence, Spray, ReactiveMongo, SBT, Kafka, ZooKeeper
- Web : NodeJS, AngularJS
- iOS : Swift, Objective C, ReactiveCocoa, Core Bluetooth, CocoaPods`
- DevOps : Ubuntu, Docker, Ruby, Amazon AWS/EC2
- Project management: git/github
The `iOS` stack is more sophisticated than the average iOS App.
It includes a Pub/Sub system similar
to `Apache Kafka` (that we call iOS Kafka internally),
makes heavy use of
asynchronous programming + `CQRS`/`Event Sourcing` and
computes biometric algorithms and reports. Our culture
===========
We get some inspiration from the Open Source model to
achieve high-cohesion (within teams) and
low-coupling (between teams) : small, empowered teams,
systematic pull requests, developer autonomy.Our software engineering practices are also influenced by Antifragile [4] principles (Small is Beautiful, Less is more, Hormesis principle, evolutionary darwinism, over-compensation ...)
And if you are on the Paleo diet, like hiking/camping or enjoy a good raclette you will certainly find friends here!
Next step
=========
If you are curious about the project and want to explore
opportunities working with us, you can
- reach out to [email protected]
- come hang out on IRC (irc.freenode.net #omsignal) to ask your questionsIf you have a `github`/`bitbucket` account, we would love to take a look at what you like doing (even if you feel ashamed of it in retrospective -- explain us what you would improve now)
Footnotes
=========
[1] http://www.omsignal.com/blogs/omsignal-blog/14669049-omsigna...
[2] http://venturebeat.com/2014/04/16/brave-new-wearable-world-c...
[3] http://www.reactivemanifesto.org/
[4] http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
Headquarters: Montreal | http://www.omsignal.com
Link to Job Offer: https://github.com/OMsignal/omsignal-job-offers/blob/master/...
OMsignal is made possible by the expertise of Smart Textile experts, Data/Bio Scientists, Hardware, Firmware and Software Engineers. Please note that this offer is mostly focused on Full Stack Engineers, but we are also looking to hire smart Data Scientists who have an interest in biodata and possibly people who could help bridging BLE/MSP firmware and driver development.
What we do
==========
OMsignal is an exciting Montreal start-up developing a revolutionary
line of bio-sensing clothes that connect seamlessly
to smartphones. The company is at the intersection of the wearable
technology, well-being and fashion markets.We are a well-funded startup [1] working to deliver a smart biometric shirt. You can read more about our mission on [2]. And for those who followed the US Open 2014, we are the technology behind Ralph Laurent Polo Tech.
We just shipped the product to our first customers.
What we are looking for
=======================
We are looking for Full Stack Software Engineers who can
help us to architect, design and implement a complex system based
on bleeding edge technologies (Scala, Akka, Spray, Reactive Programming [3],
iOS, Swift, Docker...), a modern architectural
style (Micro Services, CQRS, Event Sourcing, Eventual Consistency),
and a clean codebase (Clean Code, Domain Driven Design…) -- emphasis on
the “Engineer” over the “Full Stack” part.In-depth knowledge of the technologies we use is not required, but having strong Software Engineering foundations is (Algorithmics, Design and Architectural Patterns, …). Understanding that code is read much more often than it is written is an absolute must.
You should be willing to face the upcoming challenges (Machine Learning, Predictive algorithms, Opening the platform/iOS SDK/API, -- who knows the rest?…).
And of course, you need to speak/write english fluently (we need to understand each other, right ?)
The Technologies we currently use
=================================
- Backend : Scala, Akka, Akka Persistence, Spray, ReactiveMongo, SBT, Kafka, ZooKeeper
- Web : NodeJS, AngularJS
- iOS : Swift, Objective C, ReactiveCocoa, Core Bluetooth, CocoaPods`
- DevOps : Ubuntu, Docker, Ruby, Amazon AWS/EC2
- Project management: git/github
The `iOS` stack is more sophisticated than the average iOS App.
It includes a Pub/Sub system similar
to `Apache Kafka` (that we call iOS Kafka internally),
makes heavy use of
asynchronous programming + `CQRS`/`Event Sourcing` and
computes biometric algorithms and reports. Our culture
===========
We get some inspiration from the Open Source model to
achieve high-cohesion (within teams) and
low-coupling (between teams) : small, empowered teams,
systematic pull requests, developer autonomy.Our software engineering practices are also influenced by Antifragile [4] principles (Small is Beautiful, Less is more, Hormesis principle, evolutionary darwinism, over-compensation ...)
And if you are on the Paleo diet, like hiking/camping or enjoy a good raclette you will certainly find friends here!
Next step
=========
If you are curious about the project and want to explore
opportunities working with us, you can
- reach out to [email protected]
- come hang out on IRC (irc.freenode.net #omsignal) to ask your questionsIf you have a `github`/`bitbucket` account, we would love to take a look at what you like doing (even if you feel ashamed of it in retrospective -- explain us what you would improve now)
Footnotes
=========
[1] http://www.omsignal.com/blogs/omsignal-blog/14669049-omsigna...
[2] http://venturebeat.com/2014/04/16/brave-new-wearable-world-c...
[3] http://www.reactivemanifesto.org/
[4] http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
It's a wonder that we don't see more of these crimes, given that the rewards (if they don't get caught) accrue to the parties responsible, while the punishments (if caught) are suffered almost exclusively by everybody else. The people who made the criminal decisions do not suffer when the corporation is fined/santioned, it's shareholders, innocent employees and society at large who do. In other words, there's very little disincentive against this behavior.
What we really should consider is adding personal criminal liability to corporate officers who are found to either commit or condone financial crimes, as far up in the call stack as it can be proven.
1. http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
"What an assertion! It also proved to be very useful for hordes of scientists... what about some examples of confused scientists?"
How about every single economist and financial analyst who failed to predict the financial crashes of the last 50 years? Did you realize how much money was lost over the last 50 years by the financial industry's reliance on models that improperly use the standard Gaussian bell curve? Taleb pointed out why the Gaussian is not usually an appropriate model for financial analysis and suggested a return to more conservative models. Yet today Modern Portfolio Theory and the Black-Scholes models (which use the Gaussian) dominate in financial schools and institutions despite the fact that they absolutely utterly failed, not badly, but catastrophically in every financial crisis when they were most needed.
You state that "Standard deviation tells you how volatile measurements are". But Taleb shows how financial markets are non-Gaussian and have "fat tails" and gives the data and the supporting arguments.
bluecalm says:
"As someone who uses it daily I am eagerly awaiting his argument."
You're late! Taleb began publishing his arguments years ago and continues to publish. You're way behind. Read his papers and read his books in the following order:
Fooled by Randomness http://www.amazon.com/Fooled-Randomness-Hidden-Chance-Market...
The Black Swan http://www.amazon.com/The-Black-Swan-Improbable-Robustness/d...
Antifragile, http://www.amazon.com/Antifragile-Things-That-Gain-Disorder/...
BTW simply because someone's writing style is different does not mean that he is wrong. To me, complaining about a writing style is a form of ad hominem argument. People are different and Taleb is one-of-a-kind. Initially I didn't see where he was going, but once I realized that he was presenting ideas that were absolutely, utterly novel and had real explanatory power I sat up and paid attention. If you read for the facts and the valid arguments you will see that Taleb delivers the goods.
[1] http://www.amazon.com/Antifragile-Things-That-Gain-Disorder/...
Seeing as your professor is all knowing, maybe they could finally tell us all how lithium polymer batteries work [3]?
1: http://www.amazon.com/Antifragile-Things-That-Gain-Disorder/... 2: http://www.ted.com/talks/tim_harford.html 3: https://news.ycombinator.com/item?id=5124170
It's essentially the culmination of Fooled By Randomness and The Black Swan.
http://www.amazon.com/Antifragile-Things-That-Gain-Disorder/...
It is an enjoyable read so far...
Anyway, in short, I would never try to prepare for worst-case global scenarios because the magnitudes don't make sense for me to try to influence. Even if I was a prepper - I would have no insight into what would signal me being prepared/safe.
I try to focus a lot on optimizing my local conditions because they influence my daily life much more significantly and with much higher guarantees.
I'm in the market to buy a house in the next year or so and even asking myself the question, "Will living in <area> be a good choice in 50 years?" seems like a laughably difficult question to answer. I can look at how insurance prices are changing and historical patterns in temperature fluctuations, or I could bet on living next to civilization is better than living in the middle of nowhere, or I could bet living in a colder region is smart because it'll warm up, or I could find a warm region with geographical landscapes that insulate it from more extreme weather patterns, etc. etc.. but then what if the North Atlantic Current collapses and all the historical weather patterns are void?
In the end, I haven't found it good or healthy to try to build my life in the direction of that mindset. Instead, I strive to adopt an anti-fragile mindset and lifestyle (https://www.amazon.com/Antifragile-Things-That-Disorder-Ince...).
I want to be healthy and fit so that my body and mind are adaptable to the ever-quickening pace of the world. I want to minimize my physical and mental addictions. I want to be kind, friendly, and outgoing to those in my local community as to strengthen them and to increase the likelihood of reciprocity. I want to be comfortable with leadership, and have enough confidence to lead when I feel I can get us to good outcomes. I don't want to make decisions based off of anxiety, fear, or scarcity. I want the systems I employ in my daily life to be efficient to the point of mindlessness. I want enough money to have a couple of years of runway if I have a serious injury.
None of my strategies guarantee me survival in black swan events, but who cares? Nobody's getting out of here alive anyway. Try to not make your lived-life hellish by envisioning what a worse tomorrow could be.