True but then you increase the bundle size with all the polyfills. Honestly, I could careless but these are the things "senior" developers have told me and it turns out that there are as many opinions as there are "senior" developers.
I guess I'm just being sarcastic but it is a fact that software development industry with its "senior" developers with five years of experience has made it very toxic. Everyone thinks their opinions are facts. I have a lot to say about this, maybe I'll write a post instead someday.
In software development, everything is about balance. You don't need to use all the features all the time. Also, compilers are much smarter now, with tree shaking and all other optimizations available to us we can have very small bundles.
There are rather few things which could be proven in software development too - most of it boils down to opinions. That's the both, a burden and a blessing.
FYI, I know these terms and the concept you are talking about are quite primitive like tree shaking etc. I also understand that software engineering is very different compared to other engineering disciplines because most of it is based on abstractions. We don't have to understand how the machine works but using those abstractions we can create beautiful things.
My only problem with the development community is toxic "senior" developers that are in over their head, trying to micro-manage and enforce their opinions. Read a book or talk to an actual senior developer with 20 or 30 years of experience and you'll understand that a lot of "senior" developers that I talk about throw terms around and enforce their opinions in shallow hopes of appearing smart.
Even better if you know them already. I typically listen to people who are in this industry more than me because most of what I've read is useful. The only exception would be developers who are working industry for a long time at the same position. They typically don't learn anything new and they're just piling up years for the CV. Throwing terms around is sometimes I notice fairly often from people who aren't in this industry or are junior developers.
Not having opinions would make software development unbearable job. I have my opinions about structuring my projects, writing tests, documenting things and so on which were of course influenced by the industry standards, community and so on. We can all agree that there is no single right way to do things.
True but then you increase the bundle size with all the polyfills. Honestly, I could careless but these are the things "senior" developers have told me and it turns out that there are as many opinions as there are "senior" developers.
I guess I'm just being sarcastic but it is a fact that software development industry with its "senior" developers with five years of experience has made it very toxic. Everyone thinks their opinions are facts. I have a lot to say about this, maybe I'll write a post instead someday.
Thanks.
In software development, everything is about balance. You don't need to use all the features all the time. Also, compilers are much smarter now, with tree shaking and all other optimizations available to us we can have very small bundles.
There are rather few things which could be proven in software development too - most of it boils down to opinions. That's the both, a burden and a blessing.
FYI, I know these terms and the concept you are talking about are quite primitive like tree shaking etc. I also understand that software engineering is very different compared to other engineering disciplines because most of it is based on abstractions. We don't have to understand how the machine works but using those abstractions we can create beautiful things.
My only problem with the development community is toxic "senior" developers that are in over their head, trying to micro-manage and enforce their opinions. Read a book or talk to an actual senior developer with 20 or 30 years of experience and you'll understand that a lot of "senior" developers that I talk about throw terms around and enforce their opinions in shallow hopes of appearing smart.
Yup that throwing terms around, I have seen that a lot.
Even better if you know them already. I typically listen to people who are in this industry more than me because most of what I've read is useful. The only exception would be developers who are working industry for a long time at the same position. They typically don't learn anything new and they're just piling up years for the CV. Throwing terms around is sometimes I notice fairly often from people who aren't in this industry or are junior developers.
Not having opinions would make software development unbearable job. I have my opinions about structuring my projects, writing tests, documenting things and so on which were of course influenced by the industry standards, community and so on. We can all agree that there is no single right way to do things.
Yeah one must have opinions, just we should never force it on others.