After spending the past three weeks learning the 'ins and outs' of javascript, HTML, and CSS at Flatiron School (the coding bootcamp I'm currently attending) - we finally began our journey into React. For a little background information, I have a few friends who have been in the web dev industry for the past few years and as I began coding on my own and learning different languages, they all told me that React was something that I should definitely take a look at.
Fast forward a few months and I have finally decided to attend a coding bootcamp to pursue my goal of becoming a web developer. While going through the options - Flatiron School stood out to me as it was the only one I found offering in-person teaching at the time as well as React as a focal point.
I had seen a few examples of React from templates as well as some demonstrations on YouTube, etc. but it was a totally different experience trying to absorb all of the features and hooks as well as really understanding how to conceptualize what your website and its components should look like. However, after spending a few weeks working through countless examples and tests, I feel like I'm really beginning to break into what makes React so amazing. The organization of components, fetching info from API's with useEffect, understanding state and how to best utilize it to fit your needs - each new feature you learn seems to add another layer of understanding to web development and just how far you can take it.
Top comments (4)
Thanks to React 18 strict mode
useEffect()
had a bit of a drama last week—which coincided withWhere you can cause side effects
"In React, side effects usually belong inside event handlers. Event handlers are functions that React runs when you perform some action—for example, when you click a button. Even though event handlers are defined inside your component, they don’t run during rendering! So event handlers don’t need to be pure."
David Khourshid's endorsement of
useSyncExternalStore()
is an assertion that components should not fetch data directly—they should merely "tell" something on the other side of Context that a fetch may be necessary. That something would then later notify any subscribed components to synchronize themselves with the freshly fetched data once it arrives.He's had this position for quite some time:
PS:
In my opinion React development creates apps that "tunnel" over the web/browser.
"Facebook’s famous React library, the present-day darling of web-dev, uses HTML and javascript but abstracts the [browser itself away]. ... Facebook realizes they have no advantage in the Web over any usurper platform, and helping the Web only further enshrines their competitors. ... In a similar way as React can abstract the HTML DOM away, Facebook has abstracted HTTP away from their service stack. ... Facebook increasingly has no dependence on Web technology." Ref
Web development is more concerned with developing solutions that acknowledge and deal with the web's physical constraints (which is hopefully what Generation 3 is all about).
Hey👋,
Let me share my experience with
React
when I was new to thisAround a year back, I used to build most of my websites with
HTML
CSS
andJavaScript
. Not gonna lie, it used to be interesting during the start but everyone knows, after sometime you would be comparing your website with the ones currently on the market.When you will be checking other stuffs on internet, you would be feeling bored or low as everyone of us want our websites to look really cool right ?
That's where you find the need for frameworks and that's when I was introduced to React.
So, how's my experience and how I transformed from a noob to pro in
React
-But if you work hard, every single effort pays back
It really feels happy when you work hard and it pays off. 😊
So, my suggestion for you would be to never give up. Just try it !
Give your best !🚀
All the best 👍
Congrats! I'm just starting to look into frameworks and incorporate them so it's nice to hear it was such a game changer for you!
Good luck it gets easier over time.