Matthew Skelton > Quotes

“Sometime it's more difficult to know the question than to find an answer.”
― Matthew Skelton, Endymion Spring

“Wisdom speaks with a silent tongue.”
― Matthew Skelton, Endymion Spring

“She smiled. "How...cute." She chose the word rather like a candy, which she bit.”
― Matthew Skelton, Endymion Spring

“The safest place to hide a leaf is in a forest.”
― Matthew Skelton, Endymion Spring

“Naked we're born, naked we'll go,
See how the vain are soon brought low.
God speed the poor boy on his way,
Fear not, we'll meet some other day.”
― Matthew Skelton, Endymion Spring

“When summer and winter in autumn divide
The sun will uncover a secret inside.
Should winter from summer irrevocably part
The whole of the book will fall quickly apart.
Yet if the seasons join hands together
The order of things will last forever.
These are the words of Endymion spring.
Bring only the insight the Inside brings.

The child may see what the man does not
A future time which time forgot:
Books yet to be and books already written
Within these pages lie dormant and hidden.
Yet darkness seeks what light reveals
A shadow grows: these truths conceal.
These are my words, Endymion spring.
Bring only the insight the Inside brings.

The silence will end-the sum approaches
Mark my word-the shadow encroaches.
The present had passed-the past has gone
The future will come-once Two become One.
The sun must look the shadow in the eye
Then forfeit the book lest one half die.
The lesion of darkness cannot be healed
Until, with Child's Blood, the whole is sealed.
These are the words of Endymion spring.
Bring only the insight the Inside brings.”
― Matthew Skelton, Endymion Spring

“Wisdom comes with age and experience.”
― Matthew Skelton, Endymion Spring

“I had opened a book that could not be closed, started a story that had no obvious conclusion. It was a tale in which I wanted to play no part.”
― Matthew Skelton, Endymion Spring

“It held an eye to the future and a tongue to the past.”
― Matthew Skelton, Endymion Spring

“You can never trust the heart of another?”
― Matthew Skelton, Endymion Spring

“Love speaks with a false tongue. It kisses you in one ear, then turns with a hiss to bite the other.”
― Matthew Skelton

“Requiring everyone to communicate with everyone else is a recipe for a mess.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“building and running software systems is a sociotechnical activity, not an assembly line in a factory.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“He gazed thoughtfully at the piece of fabric in her hand. 'Hope' he said, and gave a little smile. 'A quality I should have thought you already possessed in abundance.”
― Matthew Skelton

“mature”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“If the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“We like to think that Team Topologies is another piece of this puzzle—in particular, having clear and fluid team structures, responsibilities, and interaction modes.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“The mission of a platform team is to reduce the cognitive load of stream-aligned teams by off-loading lower level detailed knowledge (e.g., provisioning, monitoring, or deployment), providing easy-to-consume services around them.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“Furthermore, the common belief that open-plan offices increase collaboration has been disputed by a field study that found that in two organizations that adopted open offices “the volume of face-to-face interaction decreased significantly (approximately 70%)”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“In order to be as effective as possible, we need to consciously design our teams rather than merely allow them to form accidentally or haphazardly.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“With stable, long-lived teams that own specific bits of the software systems, we can begin to build a stable team API: an API surrounding each team.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“Organizations should be viewed as complex and adaptive organisms rather than mechanistic and linear systems. —Naomi Stanford, Guide to Organisation Design”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“We need to look for natural ways to break down the system (fracture planes) that allow the resulting parts to evolve as independently as possible.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“Organizations which design systems . . . are constrained to produce designs which are copies of the communication”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“In many organizations, poorly defined team interactions and responsibilities are a source of friction and ineffectiveness. A team may have been told it is autonomous and self-organizing, but team members find they have to interact with many other teams in order to complete their work; and this feels frustrating. Another team may have responsibility for providing an API or service, but they don’t really have the experience to do this effectively.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“A good test for DevEx is how easy it is to onboard a new Developer to the platform.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“Reorganizations that ignore Conway’s law, team cognitive load, and related dynamics risk acting like open heart surgery performed by a child: highly destructive.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“Site Reliability Engineering is an approach to the operation and improvement of software applications pioneered by Google to deal with their global, multi-million-user systems. If adopted in full, SRE is significantly different from IT operations of the past, due to its focus on the “error budget” (namely defining what is an acceptable amount of downtime) and the ability of SRE teams to push back on poor software.”
― Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow

“bandwidth to pursue mastery of their trade and struggles with the costs of switching contexts.”
― Matthew Skelton, Team Topologies, 2nd Edition: Organizing Business and Technology for Fast Flow of Value