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
なぜ適用するか、移行して理解するClean Architecture 〜構造を超えて設計を継承する〜 / Why Apply, Migrate and Understand Clean Architecture - Inherit Design Beyond Structure
seike460
PRO
3
780
テスト駆動Kaggle
isax1015
0
300
新メンバーも今日から大活躍!SREが支えるスケールし続ける組織のオンボーディング
honmarkhunt
5
7.6k
Is Xcode slowly dying out in 2025?
uetyo
1
280
High-Level Programming Languages in AI Era -Human Thought and Mind-
hayat01sh1da
PRO
0
780
LT 2025-06-30: プロダクトエンジニアの役割
yamamotok
0
780
ISUCON研修おかわり会 講義スライド
arfes0e2b3c
1
450
AIプログラマーDevinは PHPerの夢を見るか?
shinyasaita
1
230
MDN Web Docs に日本語翻訳でコントリビュートしたくなる
ohmori_yusuke
1
130
スタートアップの急成長を支えるプラットフォームエンジニアリングと組織戦略
sutochin26
1
6k
プロダクト志向ってなんなんだろうね
righttouch
PRO
0
190
Porting a visionOS App to Android XR
akkeylab
0
480
Featured
See All Featured
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
281
13k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
29
9.6k
Building a Modern Day E-commerce SEO Strategy
aleyda
42
7.4k
The Straight Up "How To Draw Better" Workshop
denniskardys
235
140k
BBQ
matthewcrist
89
9.7k
Into the Great Unknown - MozCon
thekraken
40
1.9k
How to Think Like a Performance Engineer
csswizardry
25
1.7k
4 Signs Your Business is Dying
shpigford
184
22k
GitHub's CSS Performance
jonrohan
1031
460k
Agile that works and the tools we love
rasmusluckow
329
21k
How STYLIGHT went responsive
nonsquared
100
5.6k
Why You Should Never Use an ORM
jnunemaker
PRO
58
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 //
[email protected]
// twitter.com/skidding // github.com/skidding