"Elegant code is the end" in the real world anyone thinking that way will have a hard time working in so many places. It's a good idea as you get into any workp

"Elegant code is the end" in the real world anyone thinking that way will have a hard time working in so many places. It's a good idea as you get into any workplace to understand at least the basics about companies and their finances, and the 3 drives they have are: generate revenue, reduce costs, reduce risk. You better align your job with one of these 3, and in fact good infra is strongly correlated with reducing risk so I think this whole article could/should have been aligned around that. Also "product" unfortunately means something different, so also not the best naming... Instead I prefer to ask for clarification of the role reach. In fact just yesterday I was helping a friend who is job-hunting and I had to explain that front-end could mean since he was a bit concerned about "how deep" he needed to know React: - A person who does a bit of everything, from mockups, design, layout, components, API calls, etc. These roles are normally a jack-of-all-trades type, where it's better to be balanced and know 6/10 of each of these skills instead of focusing only on one. It's characteristic of small/lean teams, SME and people working on internal tooling. - A person who is an expert in React, working in a larger "front-end team" where there's a separated business person, designer, etc. and you only need to get those designs and build a great (Web)App. Knowing React and Javascript well is quite important. This is characteristic of large teams working on client-facing products.