Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Centralising the right things
Search
Tom Booth
June 09, 2017
Technology
1
1.3k
Centralising the right things
Tom Booth
June 09, 2017
Tweet
Share
More Decks by Tom Booth
See All by Tom Booth
Painting in Clojure
tombooth
0
130
Using data and visualisation to improve government
tombooth
0
260
Other Decks in Technology
See All in Technology
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
10k
技術キャッチアップ効率化を実現する記事推薦システムの構築
yudai00
2
170
dbt meetup #19 『dbtを『なんとなく動かす』を卒業します』
tiltmax3
0
140
入門DBSC
ynojima
0
100
Claude Cowork Plugins を読む - Skills駆動型業務エージェント設計の実像と構造
knishioka
0
230
Datadog Cloud Cost Management で実現するFinOps
taiponrock
PRO
0
100
メタデータ同期に潜んでいた問題 〜 Cache Stampede 時の Cycle Wait を⾒つけた話
lycorptech_jp
PRO
0
130
組織のSREを推進するためのPlatform EngineeringとEKS / Platform Engineering and EKS to drive SRE in your organization
chmikata
0
170
Microsoft Fabric のワークスペースと容量の設計原則
ryomaru0825
2
230
Bill One 開発エンジニア 紹介資料
sansan33
PRO
5
18k
マネージャー版 "提案のレベル" を上げる
konifar
10
3.9k
問い合わせ自動化の技術的挑戦
recruitengineers
PRO
2
110
Featured
See All Featured
How to Grow Your eCommerce with AI & Automation
katarinadahlin
PRO
1
130
Exploring anti-patterns in Rails
aemeredith
2
280
Odyssey Design
rkendrick25
PRO
2
530
Jamie Indigo - Trashchat’s Guide to Black Boxes: Technical SEO Tactics for LLMs
techseoconnect
PRO
0
79
Optimizing for Happiness
mojombo
378
71k
Being A Developer After 40
akosma
91
590k
Site-Speed That Sticks
csswizardry
13
1.1k
A Guide to Academic Writing Using Generative AI - A Workshop
ks91
PRO
0
220
Testing 201, or: Great Expectations
jmmastey
46
8.1k
DBのスキルで生き残る技術 - AI時代におけるテーブル設計の勘所
soudai
PRO
62
50k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.4k
Building an army of robots
kneath
306
46k
Transcript
@tombooth Centralising the right things Tom Booth
@tombooth
@tombooth tl;dr
@tombooth Build a central team to empower and support others
@tombooth Centralised Decentralised Re-centralised
@tombooth Centralised Decentralised Re-centralised
@tombooth
@tombooth We weren’t one business, we were compe>ng func>ons
@tombooth Protec>onism built through compe>>on
@tombooth
@tombooth Every 3 weeks, …
@tombooth
@tombooth Every 3 weeks, we had a wild ride of
forgoHen changes
@tombooth Opera>ons would get the blame for developer problems
@tombooth
@tombooth Why did their change break my code?
@tombooth Centrally provided tools were very poor
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change was complex because of poor design When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth Centralised Decentralised Re-centralised
@tombooth One team needs to own the whole service
@tombooth
@tombooth You have to embrace change
@tombooth Deploying con>nuously is beHer for users
@tombooth A team should own its own architecture and infrastructure
@tombooth
@tombooth Every team with their own direc>on, liHle shared
@tombooth Solving the same problems, in the same way with
different implementa>ons
@tombooth Opera>ng at larger scale requires deeper knowledge
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change is complex because of poor architecture When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth The same problems were being solved repeatedly When we
were decentralised,
@tombooth No-one has the complete picture When we were decentralised,
@tombooth We weren’t focusing on our users as much as
we should When we were decentralised,
@tombooth Centralised Decentralised Re-centralised
@tombooth Retain ownership in the service teams
@tombooth Iden>fy common paHerns in our infrastructure
@tombooth Support common paHerns with great tooling
@tombooth Always ask, how can we help each other?
@tombooth Give teams room to experiment, do what’s best for
them
@tombooth Outside impressions maHer
@tombooth
@tombooth Help our owners, investors and auditors understand our services
@tombooth Work together not apart
@tombooth Work together on architecture
@tombooth Work together on issues
@tombooth Work together on bugs in produc>on at 3am
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change is complex because of poor architecture When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth The same problems were being solved repeatedly When we
were decentralised,
@tombooth No-one has the complete picture When we were decentralised,
@tombooth We weren’t focusing on our users as much as
we should When we were decentralised,
@tombooth Build a central team to empower and support others