Twitter | Search | |
Frederic Barthelemy 8 Aug 18
Replying to @dan_abramov
I think beginners don’t know how anything feels, and want a guideline for where to start so they can focus on harder concepts, faster. (* me as a React beginner 8 months ago looking at those same articles)
Reply Retweet Like
Dan Abramov
It is a guideline though. It means literally “start by putting everything in one file; when it feels like it’s annoying, start splitting them up; what THAT gets annoying, maybe add some folders”.
Reply Retweet Like More
John Lombardo 8 Aug 18
Replying to @dan_abramov @fbartho
It's Annoyance Driven Development.
Reply Retweet Like
Miss Molly 9 Aug 18
I mean, isn't everything?
Reply Retweet Like
John Lombardo 14 Aug 18
That's fair. I don't remember the last time I built something because I was perfectly happy with what currently exists.
Reply Retweet Like
Mauguet PO 8 Aug 18
Replying to @dan_abramov @fbartho
I appreciate and admire how React guys try not to be too directive or not to load React with inappropriate responsabilities. It would be much simpler to give absolute lessons by community mentors but I feel there's no absolute in development.
Reply Retweet Like
Nick Trabue 8 Aug 18
Replying to @dan_abramov @fbartho
Reply Retweet Like
Ivan Babak 8 Aug 18
Replying to @dan_abramov @fbartho
This your tweet should be on that website instead.
Reply Retweet Like
Ethan R 9 Aug 18
Replying to @dan_abramov @fbartho
Start with one file. Finish with one file 😎👌
Reply Retweet Like
Colin Morgan 8 Aug 18
Replying to @dan_abramov @fbartho
This is exactly how I approach fleshing out a react project. Start with one file and refactor into separate files as it feels necessary. Feels nice and organic.
Reply Retweet Like
Kevin Clark, Web Dev 🏁 8 Aug 18
Replying to @dan_abramov @fbartho
I have started the opposite by trying to divide everything into a perfect structure and it slows me down....now I like to start by having less separation
Reply Retweet Like
Ben McCallum 8 Aug 18
Replying to @dan_abramov @fbartho
This is the approach I take for Visual Studio solutions (.NET) too. Too many people think it's a good idea to abstract out into layers with different projects when foldering logically is enough until you need more or to share.
Reply Retweet Like
TheDevCouple {Awais, Maedah} 9 Aug 18
Replying to @dan_abramov @fbartho
The HUGE problem with this approach is that not everyone is intuitive.
Reply Retweet Like
Gabriel Wu 6 Sep 18
Replying to @dan_abramov @fbartho
Actually I was told to put everything in one file by the Elm official tutorial lol
Reply Retweet Like
Michael Olie 8 Aug 18
Replying to @dan_abramov @fbartho
Sick
Reply Retweet Like
Ashishkumar Pandey 8 Aug 18
Reply Retweet Like
Dan 8 Aug 18
Replying to @dan_abramov @fbartho
Honest truth I think I have to do this often as the project grows and patterns form
Reply Retweet Like
Daniel Kaspo (NessDan) 9 Aug 18
Replying to @dan_abramov @fbartho
Oh geez, all my variables are in separate files and I can't find where I placed my store... Please advise!
Reply Retweet Like
Gemma Black 9 Aug 18
Replying to @dan_abramov @fbartho
😑 lol
Reply Retweet Like
Huang 29 Aug 18
Replying to @dan_abramov @fbartho
wisdom bomb!
Reply Retweet Like