silos
turf wars
Open source & the destruction of jurisdiction make scalability
possible.
Speaking of history...
finger pointing
prescriptive
More advice:
buying achieves
scale
availability
accelerated time to market
less distraction for in-demand resources
collective product advancement
deep knowledge for non-core domains
lack of access
requirements
to developers
criticalness
uniqueness
lack of access
of
service delivery
relative to your industry
to code
Separate
postponed
except
buying is a
ongoing
time to market
There is really no downside to adoption, when the only available products are not open or do not exist or are crap.
building is a
maintenance burdens
lack of control
your problems:
huge risk...
over the product roadmap
huge risk...
building achieves
myopic view
competitive advantage
intellectual property value
internal expert knowledge
adoption
of the problem (and solutions)
Ask yourself:
Why should I build things myself?
well defined,
Roles were
duties were
separated,
Understand that one
can only have
so much expertise...
Understand your problem space.
Understand your technology.
Buy
Become an expert.
choose carefully.
open source
vs
but...
I can't publish packages.
Network issues.
Hardware checksum errors.
3
operating systems
Build
gave us
Imagine this process with silos or without code.
There are a lot of
answers.
bad
6
vs
programming languages
Rant:
Adopt
50MM
Users
Rebuild the world.
Unicode in the perl source.
30
git repos
highly complex
Scalable systems
fixes to open-source projects per month
are...
libssh2
openssl ABI issues
highly decoupled
engineers did what they had to do:
There is one truth...
Combining this with the
need to scale ?
and it is rather inconvenient.
"huge"
they built it themselves.
highly
messy
tend to fail
Decoupled systems across (not on) their elegant boundaries.
"Jack of all trades; master of none."
buy vs. build
If the boundaries are violated,
being responsible requires more.
A very old (and still very hard) question
Without access to
source code...
& thus no way to fix it
That Truth is:
You Own What You Deploy
Someone has to be
responsible.
This means jurisdictions break down.
If the boundaries are elegant and unbroken,
that someone can be anyone.
Engineers must know more pieces.
(or replicate)
Capable of transcending the whole stack.
running
Those that were
the software...
bottom
Acknowledgements
Pointer designed by Evan MacDonald from The Noun Project
Hammer designed by John Caserta from The Noun Project