In this video I talk about programming. This video is part of my vlog series where I explain my way of thinking about topics related to software development.
When we hired I didn't ask for CVs and did interviews with everyone who applied. It was a blast. I've met a lot of awesome people, like NASA grade. We wouldn't even need to do interviews a second time because we were already in contact with great people. Also, I don't understand why the need for software developers to be this grandiose machine capable of dealing with all the architecture of a business. It's ok not to know everything and it's the company's job to split the work in approachable chunks.
I agree with the scalabity indicator. There are many developers who do not have any experience in large scale production systems maintained for years. These people are not of my interest. Their experience practically boils down to the mid level at most.
And why is that a problem? Did your architects leave and nobody knows how the business runs anymore? Why would your developers need to know your whole 30 APIs and 25 adapters? Also how your accounting works and let's not forget your Google campaigns. Developers build tools that your business defines. They build hammers and saws. If the business hurts itself with them, it's not the developer's fault.
@@redguard128a lack of experience means more costs and effort and slower throughput of teams. It's not just some api. It's technological versatility that is lacking. Working with large production systems requires a deeper understanding of how technologies behave. Some people have never learned that. Other projects are suitable for them.
Here is a repo I made that covers most of the tools and practices in larger companies. You can switch the backend language for anything, usually C# or Java are popular. The rest is imo still true today. github.com/fChristenson/js-roadmap
When we hired I didn't ask for CVs and did interviews with everyone who applied. It was a blast. I've met a lot of awesome people, like NASA grade. We wouldn't even need to do interviews a second time because we were already in contact with great people.
Also, I don't understand why the need for software developers to be this grandiose machine capable of dealing with all the architecture of a business. It's ok not to know everything and it's the company's job to split the work in approachable chunks.
I agree with the scalabity indicator. There are many developers who do not have any experience in large scale production systems maintained for years. These people are not of my interest. Their experience practically boils down to the mid level at most.
And why is that a problem? Did your architects leave and nobody knows how the business runs anymore? Why would your developers need to know your whole 30 APIs and 25 adapters? Also how your accounting works and let's not forget your Google campaigns.
Developers build tools that your business defines. They build hammers and saws. If the business hurts itself with them, it's not the developer's fault.
@@redguard128a lack of experience means more costs and effort and slower throughput of teams. It's not just some api. It's technological versatility that is lacking. Working with large production systems requires a deeper understanding of how technologies behave. Some people have never learned that. Other projects are suitable for them.
Hi Fredrik, thanks for providing value as always. I'd be interested in seeing that video - @12:49
Here is a repo I made that covers most of the tools and practices in larger companies.
You can switch the backend language for anything, usually C# or Java are popular.
The rest is imo still true today.
github.com/fChristenson/js-roadmap
@@FredrikChristenson Thank you so much