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
Admin Your App
Search
Michael Becker
March 24, 2014
Technology
1
110
Admin Your App
Michael Becker
March 24, 2014
Tweet
Share
More Decks by Michael Becker
See All by Michael Becker
Intro to Ember
michaelseanbecker
0
54
Other Decks in Technology
See All in Technology
AIと新時代を切り拓く。これからのSREとメルカリIBISの挑戦
0gm
0
850
【5分でわかる】セーフィー エンジニア向け会社紹介
safie_recruit
0
42k
2人で作ったAIダッシュボードが、開発組織の次の一手を照らした話― Cursor × SpecKit × 可視化の実践 ― Qiita AI Summit
noalisaai
1
380
ClickHouseはどのように大規模データを活用したAIエージェントを全社展開しているのか
mikimatsumoto
0
210
セキュリティについて学ぶ会 / 2026 01 25 Takamatsu WordPress Meetup
rocketmartue
1
290
Embedded SREの終わりを設計する 「なんとなく」から計画的な自立支援へ
sansantech
PRO
3
2.3k
Amazon S3 Vectorsを使って資格勉強用AIエージェントを構築してみた
usanchuu
3
440
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
10k
入社1ヶ月でデータパイプライン講座を作った話
waiwai2111
1
270
Claude_CodeでSEOを最適化する_AI_Ops_Community_Vol.2__マーケティングx_AIはここまで進化した.pdf
riku_423
2
520
モダンUIでフルサーバーレスなAIエージェントをAmplifyとCDKでサクッとデプロイしよう
minorun365
4
170
マーケットプレイス版Oracle WebCenter Content For OCI
oracle4engineer
PRO
5
1.6k
Featured
See All Featured
Side Projects
sachag
455
43k
4 Signs Your Business is Dying
shpigford
187
22k
Between Models and Reality
mayunak
1
180
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
Deep Space Network (abreviated)
tonyrice
0
47
Max Prin - Stacking Signals: How International SEO Comes Together (And Falls Apart)
techseoconnect
PRO
0
84
Collaborative Software Design: How to facilitate domain modelling decisions
baasie
0
140
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
359
30k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
196
71k
GraphQLの誤解/rethinking-graphql
sonatard
74
11k
Why Mistakes Are the Best Teachers: Turning Failure into a Pathway for Growth
auna
0
51
The Mindset for Success: Future Career Progression
greggifford
PRO
0
230
Transcript
Admin Your App or Why Internal Tools Matter
Hi. I’m Mike. (Michael Sean Becker)
Content Engineering
None
None
None
None
I’d like to tell you a story
2012
Initial Build • Rails for backend and frontend • Active
Admin
Then RailsConf 2012 Happened
None
The Ecosystem • Smaller systems that talk to each other
• API Endpoints that served both Web and Mobile • and….. • Active Admin in the same spot as before
We modified our architecture, but didn’t update how we dealt
with internal tools.
• Admin wasn’t updated • Content creators were blocked •
Engineers had to begin updating content
That brings us to 2014
Principles • API driven • Testable • Trackable • Administrable
Our new goals • Internal users deserve good tools •
Treat our data as content and not rows in a spreadsheet • Admin tools need to be easy to add to and extend by other developers
Internal Products and Tools can be as important as the
ones you build for your customers
The Plan • Small, reusable libraries for common functionality •
Done with Ember Components when possible • Consolidated code
The Other Side • Use an establish CMS • Fix
Active Admin installation • Use our admin tools to experiment with new technology
What next? • Building our admin tools from scratch •
Start moving features over one at a time • Starting with moving the blog into our ecosystem
Things we need to solve • Isolating feature code •
Bower to make admin sections
Thank You @michaelsbecker www.michaelseanbecker.com