It's so helpful that the #react documentation talks about when to use `getDerivedStateFromProps()` in its documenation https://reactjs.org/docs/react-component.html#static-getderivedstatefromprops
I was about to use this method for a debounced search field, which would have probably lead to disappearing text bugs.
Their proposed 'fully uncontrolled component with a key' was a much neater solution.
To those of you who are part of large developer teams, what techniques do you use to keep the master branch stable?
I know the gitflow workflow is something we can try https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
Do you also do other things? Not necessarily git workflows.
There's easy learning, where you get spoon-fed by watching a course, and hard learning, where you go solve a problem or build stuff.
There are also two traps to avoid while doing hard learning:
- the researcher trap, where you get lost in documentation and not finish anything.
- the stack overflow trap, where you just copy paste and don't understand the solution.
Pair programming is a good middle-ground.
"We become what we behold".
It's an awesome 5-minute sort-of-game by Nicky Case. A pertinent commentary on journalism and how it influences our behavior, and the timing was perfect.
Also, it's open source!
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!