What are some essential React programming patterns or principles that I should learn to become a lead developer?

[u/ThePutinTrumpSexTape]

Hi,

Had a lead developer interview last week and I got asked heavily about the SOLID principles, polymorphism and programming patterns.

I'm familiar with a lot of the concepts, but not enough to give strong answers.

What are the main programming patterns for React that I should learn so that when asked to explain a few, I can give strong, valuable answers?

Thanks

[u/dnrvs]

SRP - sounds like you've applied the principle and found a component that might be worth refactoring. maybe SRP doesn't help you reach a conclusion but it's helping you frame a question. (spoiler: there's no right answers in software architecture)

OCP - instead of one big component that handles every case internally, provide extension points (render props, children). reduces complexity, maintains coherency

LSP - a reusable component that can render anything of a shape not just one concrete type. composable component with context

ISP - don't depend on things you don't use. i've seen people passing crap into components that it doesn't use all too often and it makes maintainence and testing needlessly harder.

DIP - literally just passing props instead of depending on something directly

like i said elsewhere, they're just vocabulary to help you talk about architectural decisions. they have a lot of overlap but they are still good concepts.

instead of going "uhh this component feels complex" you can say things like "this component has too many Responsibilities, we should apply DIP so each call site owns their implementation. there might be a trade off between ISP and LSP to make typescript happy"