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
デザイナーが Androidエンジニアに 挑戦してみた
874wokiite
0
200
速いWebフレームワークを作る
yusukebe
5
1.7k
個人軟體時代
ethanhuang13
0
320
Kiroの仕様駆動開発から見えてきたAIコーディングとの正しい付き合い方
clshinji
1
200
MCPで実現するAIエージェント駆動のNext.jsアプリデバッグ手法
nyatinte
7
1.1k
Azure SRE Agentで運用は楽になるのか?
kkamegawa
0
1.7k
Design Foundational Data Engineering Observability
sucitw
3
180
Oracle Database Technology Night 92 Database Connection control FAN-AC
oracle4engineer
PRO
1
430
Tool Catalog Agent for Bedrock AgentCore Gateway
licux
6
2k
アプリの "かわいい" を支えるアニメーションツールRiveについて
uetyo
0
210
パッケージ設計の黒魔術/Kyoto.go#63
lufia
3
430
MCPでVibe Working。そして、結局はContext Eng(略)/ Working with Vibe on MCP And Context Eng
rkaga
5
2.1k
Featured
See All Featured
4 Signs Your Business is Dying
shpigford
184
22k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
53k
The Cult of Friendly URLs
andyhume
79
6.6k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.9k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
61k
Automating Front-end Workflow
addyosmani
1370
200k
The Pragmatic Product Professional
lauravandoore
36
6.9k
Producing Creativity
orderedlist
PRO
347
40k
A Tale of Four Properties
chriscoyier
160
23k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
139
34k
Agile that works and the tools we love
rasmusluckow
330
21k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
36
2.5k
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