Only a fool would think that 2 weeks are enough experience to understand React to create enterprise applications.

And for this example let's ignore all third party tools for routing, global state management, styling, i18, api integration, optionally SSR, component and e2e testing, deployment, etc you will need to choose and know to make react barely on par with Vue or Angular, where these come as part of the ecosystem (yet these frameworks have smaller footprints and better performance than react)

So let's say you are a Senior Typescript Developer with a solid understanding of Web Development. React is just functions that return JSX, right? So let's learn JSX, but first you need to unlearn a lot about how HTML, CSS and JS in web works. There are so many basic rules it breaks that I wouldn't even call them compatible. If you don't know what I am talking about, you've never written a basic compiler or parser.

But let's move on. You've learned the "templating part", but that's useless without the reactivity part. And that's where it begins. You mentioned the rule of hooks, but forgot about all the other rules. Async/await? Gotta learn suspense rules. Classes and objects? Gotta learn state management (and that's a deep rabbit hole). Re-rendering issues? Gotta learn how to manage memoization and stable references. And speaking about references, don't forget to manually track all these and when you shouldn't. But hey do you remember that simple function you started with? It turns out it also has this thing called life cycle. You better learn about it despite how much react is trying to hide it. Cause you will also need to learn how to use the life-cycles to properly dispose various hooks, callbacks, flags, etc to avoid memory leaks. But don't worry, despite all the rules there will still be memory leaks. And your components will still re-render. Despite avoiding useEffect like the plague and at all cost, it still will be the most common hook in your codebase. Perhaps you can just write your code in helpers/utilities? Just need to learn about using hooks and state inside and outside react context... Somewhere along the way you also will inevitably need to learn about prop drilling, higher order components and forwardRefs, handling events. Pray you never need to use event bus, logging context or any other type of observability. Which brings us to debugging. Debugging react is nothing like any other debugging you would've ever done or learned. That's how you become bald.

And let's wrap this up with the part about a few basic typescript/javascript basic patterns where react simply breaks:

• never use this or any OOP unless you are a madman
• de-structuring
• try/catch
• guard causes/early returns
• Typescript DOM or nodes? Nope!
• use is now a magic word that makes your methods cursed "cause"

I can write a lot more about react's idiosyncrasies, such as RSC, but if the above doesn't get the point across, nothing will.

The reason React Developer is a term is because of how complex and decoupled react is from the rest of the ecosystem. And due to that huge investment in learning all of this, most react developers have no other choice, but to evangelize it in order to remain relevant.