I disagree with the idea of on an employee's first day expecting a pull request. I'd rather give the person a day to familiarise themselves with my team's coding practices and fix the bug keeping true to the practices than make them fix the bug without implementing any of the team's practices, potentially making it harder to work with the code in the future
heh, even 'having' a git guru or 3 often doesnt matter. Everybody thinks they know best even when they're clueless and too few will listen to others...
Not sure how you inferred that from the video. To me he just seemed confident and relaxed. The actual talk was pretty interesting, although it felt a bit dry.
I agree, the speaker has very interesting things to say, especially when he talked about querying and the concept of keywindows. (I didn't like the naming though)
Not really if you use it correctly. You could basically do all these things he talks about with a handful or reducers and then you dont have to care about caching at all. Just disable caching on your get-requests and let the store work in your favor. We started to rebuild our platform at work in react using the "new" context api but it gets messy after a while. I prefer redux. People that write redux with much boilerplate would have written a lot of boilerplate no matter what lib or context api you use.
This topic was insightful. I am facing some of the challenges you are facing and I can feel your frustration. Thank you for sharing!
Wow this was insightful. I really needed this.
@@adrienzachary946 what?
thanks, great video.
I disagree with the idea of on an employee's first day expecting a pull request. I'd rather give the person a day to familiarise themselves with my team's coding practices and fix the bug keeping true to the practices than make them fix the bug without implementing any of the team's practices, potentially making it harder to work with the code in the future
Fetching data in componentWillMount is known to be bad practice.
what's bad about it?
You fetch data typically in the componentDidMount() {}
@@alexmachin1785 but why do we typically do so?
is there a technical reason or is it just a convention?
heh, even 'having' a git guru or 3 often doesnt matter. Everybody thinks they know best even when they're clueless and too few will listen to others...
My developers.... me only decide..... what a person... yuck
Arrogant and selfish speaker... no respect to audience ... with bad humor... (
It's called sarcasm and irony, you should look it up.
Why do you care as a visitor if the speaker is arrogant ans selfish? Why not criticise the actual things he says?
Not sure how you inferred that from the video. To me he just seemed confident and relaxed. The actual talk was pretty interesting, although it felt a bit dry.
I agree, the speaker has very interesting things to say, especially when he talked about querying and the concept of keywindows. (I didn't like the naming though)
cry baby developer spotted
Redux adds so much bloat, just use the context if needed or pass props.
Not really if you use it correctly. You could basically do all these things he talks about with a handful or reducers and then you dont have to care about caching at all. Just disable caching on your get-requests and let the store work in your favor. We started to rebuild our platform at work in react using the "new" context api but it gets messy after a while. I prefer redux. People that write redux with much boilerplate would have written a lot of boilerplate no matter what lib or context api you use.