Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of RAMP Keynote
Open source & the destruction of jurisdiction make scalability
we do so through
most things were
Those that were
engineers did what they had to do:
Without access to
Combining this with the
need to scale ?
Decoupled systems across (not on) their elegant boundaries.
This means jurisdictions break down.
Capable of transcending the whole stack.
buy vs. build
A very old (and still very hard) question
buying is a
of the problem (and solutions)
There is really no downside to adoption, when the only available products are not open or do not exist or are crap.
accelerated time to market
less distraction for in-demand resources
collective product advancement
deep knowledge for non-core domains
intellectual property value
internal expert knowledge
Why should I build things myself?
There are a lot of
There is one truth...
and it is rather inconvenient.
Someone has to be
If the boundaries are elegant and unbroken,
If the boundaries are violated,
That Truth is:
fixes to open-source projects per month
What does the
large scale Internet architecture
openssl ABI issues
Imagine this process with silos or without code.
Understand your problem space.
Understand your technology.
Understand that one
can only have
so much expertise...
"Jack of all trades; master of none."
A long time ago,
Speaking of history...
Pointer designed by Evan MacDonald from The Noun Project
on the software in ways the vendors couldn't imagine.
& thus no way to fix it
they built it themselves.
there was a
Rebuild the world.
Unicode in the perl source.
I can't publish packages.
relative to your industry
Become an expert.
lack of visibility
tend to fail
lack of control
over the product roadmap
lack of access
lack of access
time to market
that someone can be anyone.
being responsible requires more.
You Own What You Deploy
Hammer designed by John Caserta from The Noun Project
Engineers must know more pieces.
building is a
Hardware checksum errors.