Started from notepad, now i'm here.
Consulting for Startups in San Francisco while working on a few products for the maker community
codersnippets.com javacriptpros.com formakersbymakers.com
Location
San Francisco
Work
Founder & Head of Engineering at For Makers, by Makers
Do not feel the need to extract everything into a component, yet alone things that won't be reused much.
I tend to build on projects right from the App.js initially, as you mentioned. I only extract once I find myself reusing bits of code (time for a component) or wanting to isolate state and functionality for a larger piece of the app.
This is good for a starting point, but it's important to note that large, hard-to-read files you didn't split up, just because you didn't see a case for code reuse, are the opposite of simple.
Started from notepad, now i'm here.
Consulting for Startups in San Francisco while working on a few products for the maker community
codersnippets.com javacriptpros.com formakersbymakers.com
Location
San Francisco
Work
Founder & Head of Engineering at For Makers, by Makers
KISS always, till you need to add complexity.
Do not feel the need to extract everything into a component, yet alone things that won't be reused much.
I tend to build on projects right from the App.js initially, as you mentioned. I only extract once I find myself reusing bits of code (time for a component) or wanting to isolate state and functionality for a larger piece of the app.
This is good for a starting point, but it's important to note that large, hard-to-read files you didn't split up, just because you didn't see a case for code reuse, are the opposite of simple.
Yep, after a certain point, it's worth extracting simply from a hierarchical and organizational standpoint ✊🏻