Some good points as always, but I think your personal bias shows. Your bias is towards individual greatness. A better way to look a this is how to create a system inside the company that gets productivity out of what it has
Good point. And quite often these, so called 'rock start' developers get bored pretty quickly if you don't have a challenging enough role for them. Most projects, at least in my experience, get rather mundane and boring. I think it's also a another challenge to keep that fire going. And also, many don't want to be in a leadership position or have pretty low soft skills.
I think so too, personally I think it's due the mass (UA-cam) and generally speaking mass media content where creators found out that people are easily attracted by keywords such as (high salary, full remote, computer). Obviously after the content consumer finds out that it requires consistency and certain approach to thinking, he's easily demotivated and he'll forget that idea of being a developer as fast as he discovered it. The rest which divides into two categories where the first one finds the easiest way to get even a little bit closer to the "programming empire" which is obviously web development. And the second one (which is a drastic minority) where we can observe the very little count of individuals who have enough persistence and pasion for learning regardless the paycheck. P.S. sorry for my English
@@zz-if1ic almost every company I've interviewed for asked me if I knew react native cuz they wanted someone to build a mobile app. Needless to say that react native sucks. So, if you know something like kotlin, you should be in high demand my friend.
So you are basically proposing implementing a technocracy within a software company. Have the leadership be a small group of elite people who possess expertise that the general public lacks. I don't think this would work in the majority of companies out there...
Isn’t that what faang companies do? Have highly skilled teams develop standards and practices for the overall company? So you end up with a company like Google having most of its teams using gRPC instead of REST. I could be wrong, but that’s what it looks like from the outside looking in.
@@tasheemhargrove9650 I don't think all the devs within FAANG companies are happy with the internal standards and tools. They just deal with it and wipe their tears with all the money they make. And most companies do not have the resources of FAANG. If your company would just appoint the best performing people to establish standards that MUST be followed by everyone, do you think that would go well and everyone would be happy?
The legal system seems to work well enough but if it makes us happy, hard to say. I am not sure we want to find out what happens when everyone makes their own laws. It always strikes me as odd that people who have a problem with authority highlight when things go bad yet whenever I use React, Kubernetes, Docker, a programming language, a spoken language, Math, or any other solution that makes my life easier yet forces me to do things their way I wonder why no one rebels against these systems of oppression. Perhaps we should recall the good old days when the browser wars forced us all to create 3 different ways of doing the same thing if we needed to support IE and Safari or when you needed to remember the IP of a domain because no one could agree on how dns should work. I am glad that systems of oppression like the metric system hasn't taken over.
@@FredrikChristenson I think that giving a small group of rockstar developers the power to decide standards for building software within a company is exactly the way in which you end up having multiple bad solutions to the same problem within the industry. Different teams will always come up with different ways of doing things, with the best solution being somewhere in between all of them. Projects like React and K8s were successful because they were open sourced and accepted criticism and contributions from the whole industry rather than keeping them as the brain child of a few talented devs within the companies that created them. So my point is that standardization works only when the majority of people in the industry can contribute and agree to a compromise. If every company just appoints its rockstar devs to appply standards within the company, we'll just end up adding more redundant abstractions and complexity to an industry that already suffers from too much of those. Btw, thanks for replying Fredrik, this is an interesting debate :)
Some good points as always, but I think your personal bias shows. Your bias is towards individual greatness. A better way to look a this is how to create a system inside the company that gets productivity out of what it has
Good point. And quite often these, so called 'rock start' developers get bored pretty quickly if you don't have a challenging enough role for them. Most projects, at least in my experience, get rather mundane and boring. I think it's also a another challenge to keep that fire going.
And also, many don't want to be in a leadership position or have pretty low soft skills.
have you met companies that search for developers they can abuse? I mean pay them less than they cost?
I feel like it's oversaturated with front-end/web developers. Mobile development or Unity, or HTML5 Game development are not oversaturated.
I think so too, personally I think it's due the mass (UA-cam) and generally speaking mass media content where creators found out that people are easily attracted by keywords such as (high salary, full remote, computer). Obviously after the content consumer finds out that it requires consistency and certain approach to thinking, he's easily demotivated and he'll forget that idea of being a developer as fast as he discovered it.
The rest which divides into two categories where the first one finds the easiest way to get even a little bit closer to the "programming empire" which is obviously web development.
And the second one (which is a drastic minority) where we can observe the very little count of individuals who have enough persistence and pasion for learning regardless the paycheck.
P.S. sorry for my English
@@zz-if1ic almost every company I've interviewed for asked me if I knew react native cuz they wanted someone to build a mobile app. Needless to say that react native sucks. So, if you know something like kotlin, you should be in high demand my friend.
2:38 A man that uses what is essentially inline CSS can’t talk about CSS?! My confidence grew by about 5% hearing that 😅
Do you think the C# market is still growing, that it would be a good idea as a junior developer yo try to get his first job on it?
So you are basically proposing implementing a technocracy within a software company. Have the leadership be a small group of elite people who possess expertise that the general public lacks. I don't think this would work in the majority of companies out there...
Isn’t that what faang companies do? Have highly skilled teams develop standards and practices for the overall company? So you end up with a company like Google having most of its teams using gRPC instead of REST. I could be wrong, but that’s what it looks like from the outside looking in.
@@tasheemhargrove9650 I don't think all the devs within FAANG companies are happy with the internal standards and tools. They just deal with it and wipe their tears with all the money they make. And most companies do not have the resources of FAANG. If your company would just appoint the best performing people to establish standards that MUST be followed by everyone, do you think that would go well and everyone would be happy?
The legal system seems to work well enough but if it makes us happy, hard to say. I am not sure we want to find out what happens when everyone makes their own laws.
It always strikes me as odd that people who have a problem with authority highlight when things go bad yet whenever I use React, Kubernetes, Docker, a programming language, a spoken language, Math, or any other solution that makes my life easier yet forces me to do things their way I wonder why no one rebels against these systems of oppression.
Perhaps we should recall the good old days when the browser wars forced us all to create 3 different ways of doing the same thing if we needed to support IE and Safari or when you needed to remember the IP of a domain because no one could agree on how dns should work. I am glad that systems of oppression like the metric system hasn't taken over.
@@FredrikChristenson I think that giving a small group of rockstar developers the power to decide standards for building software within a company is exactly the way in which you end up having multiple bad solutions to the same problem within the industry. Different teams will always come up with different ways of doing things, with the best solution being somewhere in between all of them.
Projects like React and K8s were successful because they were open sourced and accepted criticism and contributions from the whole industry rather than keeping them as the brain child of a few talented devs within the companies that created them.
So my point is that standardization works only when the majority of people in the industry can contribute and agree to a compromise. If every company just appoints its rockstar devs to appply standards within the company, we'll just end up adding more redundant abstractions and complexity to an industry that already suffers from too much of those.
Btw, thanks for replying Fredrik, this is an interesting debate :)