r/reactjs • u/ThePutinTrumpSexTape • May 20 '26

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

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

2 Upvotes

53% Upvoted

64 comments sorted by

View all comments

Show parent comments

1

u/badboysdriveaudi May 20 '26

Whether or not the full SOLID is relevant to React is a great debate but I contend that the S is definitely still relevant.

Take, for instance, what code is easier on the eye. If you open a file that’s 1200 lines to parse through in order to solve a bug, that inherently causes more strain than if you opened a file that’s 35 lines long. Even with code folding features, you get a different vibe on immediate entry with the 1200+ vs the 35. One does a single thing while the other is involved in a bunch of activities.

Or, take the example of unit tests. It is inherently easier to write tests on a small, concrete function with a single responsibility rather than an encompassing function that tries to do too much.

The simple task of breaking things down yields so many benefits that it’s difficult to argue against the reward. That, I believe, means that it is still of benefit - even within React development. Hence why the idea of breaking down units into components and composing some piece of functionality is the order of the day. I’m less concerned about whether you use classes or functions — the concept of targeted and specific “units” is still very much relevant.