19th October 2017, 6:00 pm
I sure like managing state with setState. But for data like entities and business logic in general you have to keep that stuff in one place, not across components.
How do you get that data to all the places that you need? Should context become a first-class react feature instead of a "dangerous experimental" one? I can think of so many uses for context... but kinda reluctant to use it all over since it has this status of being reserved until you "really-really-really" need it.
Or maybe something crazy like throwing that data into portals? :)
Passing props deeply seems to make all the sense even for complex widgets, but not for any app that's medium-to-large in scale.
How do you "discover" and assess new patterns in such libraries like React?
Throughout the past few years, we've seen cool and exciting new patterns like Higher Order Components, render props, function-as-children, and now render callback functions; despite having access to the relatively simple and straightforward React API docs, I still find it interesting and sometimes mind-blowing that devs find these new ways of composing components.
How do you personally discover potential new patterns? How do you assess patterns that other people have found/created for viability?
I am a b.tech graduate in CSE. But, I developed an interest in writing and I hold 2 years of work experience in technical content writing. Presently, I feel like I am wasting my technical knowledge and I would like to make my career in software development. Would it be possible now, with 4 years of a gap after graduation?