3 ms·
I guess I think it's table stakes to need to deeply understand how the framework you're using works. Lifecycle methods vs. hooks, you still gotta know what's do
by ervine 5mo ago
I guess I think it's table stakes to need to deeply understand how the framework you're using works. Lifecycle methods vs. hooks, you still gotta know what's doing what and why.
- halflife 5mo agoOf course, but that really depends on the level of expertise and the type of programmer you are, and to some extent, the attitude of the organization your in to code and refactoring. When everyone around writes shit code, you don’t care. In hooks, it becomes much more critical.
- ervine 5mo agoNo, writing shit in react is gonna be a nightmare regardless of paradigm. HoC, Class Components, render props, whatever - if you don't know what you're doing and react internals are magic to you, it's game over. Anyway, we can agree to disagree on hooks vs. classes. Cheers.
- halflife 5mo agoAgreed. In the end, I always say that every line of code has deadline in which it will be removed.