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
Maintainable React UIs using Cosmos.js
Search
Ovidiu Cherecheș
April 28, 2015
Programming
3
250
Maintainable React UIs using Cosmos.js
Ovidiu Cherecheș
April 28, 2015
Tweet
Share
Other Decks in Programming
See All in Programming
AIと”コードの評価関数”を共有する / Share the "code evaluation function" with AI
euglena1215
1
180
スタートアップの急成長を支えるプラットフォームエンジニアリングと組織戦略
sutochin26
1
7.4k
Git Sync を超える!OSS で実現する CDK Pull 型デプロイ / Deploying CDK with PipeCD in Pull-style
tkikuc
4
380
Jakarta EE Meets AI
ivargrimstad
0
120
20250704_教育事業におけるアジャイルなデータ基盤構築
hanon52_
5
1.1k
Rails Frontend Evolution: It Was a Setup All Along
skryukov
0
290
バイブコーディング超えてバイブデプロイ〜CloudflareMCPで実現する、未来のアプリケーションデリバリー〜
azukiazusa1
2
610
20250708_JAWS_opscdk
takuyay0ne
2
130
Goで作る、開発・CI環境
sin392
0
270
副作用と戦う PHP リファクタリング ─ ドメインイベントでビジネスロジックを解きほぐす
kajitack
2
230
DMMを支える決済基盤の技術的負債にどう立ち向かうか / Addressing Technical Debt in Payment Infrastructure
yoshiyoshifujii
4
440
顧客の画像データをテラバイト単位で配信する 画像サーバを WebP にした際に起こった課題と その対応策 ~継続的な取り組みを添えて~
takutakahashi
4
1.3k
Featured
See All Featured
Rails Girls Zürich Keynote
gr2m
95
14k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
234
17k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
60k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.6k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
Imperfection Machines: The Place of Print at Facebook
scottboms
267
13k
KATA
mclloyd
30
14k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
45
7.5k
The Cult of Friendly URLs
andyhume
79
6.5k
Making the Leap to Tech Lead
cromwellryan
134
9.4k
Transcript
Hello.
Why do UI devs change frameworks so often?
Why do UI devs change frameworks so often? A. Because
we constantly want to learn new stuff B. Because web browsers have evolved a lot in the last years or...
C. Because a change in the old framework feels like
this:
So you found a new framework... "This time it's going
to be different."
Things are going great... • Trying & learning new stuff
every day • No technical debt and haunting hacks • No need to refactor with every feature
This (framework) might be the one.
2 years later...
Why do we have so many bugs?
Why is writing code so hard to debug?
Don't be naive. React is not your soulmate.
What makes a codebase go bad in time?
None
None
How to understand an implicit codebase: 1. Grep the entire
project for that entity 2. Grep the entire project for the file name 3. Ask a friend, or... 4. ...read the entire source code.
You have to understand the entire project to figure out
something in a module. This is not scalable.
A maintainable codebase is explicit and intuitive.
How do you write explicit code? • Dependencies should be
expressed inside- out • Every module should expose a standalone, testable API • Every UI component should be an entry point.
Maintainable React UIs using Cosmos.js Bear with me...
ComponentTree Serialize and reproduce the state of an entire tree
of React components.
ComponentPlayground Minimal frame for loading and testing React components in
isolation.
Demo.
Thank you! // Ovidiu Cherecheș // Leading the Analytics UI
at Hootsuite // ovidiu.chereches@hootsuite.com // twitter.com/skidding // github.com/skidding