I would so wish that the real world would function like this :( but we can only strive to do better.
Companies are shifting away from hiring for specific programming skills and know-how in lieu of finding candidates who are adaptable and quick to learn on their feet.
I'm currently in the candidate role, in more EU countries, and I can tell you that it is only a fairy tale. It applies to huge corporations like Google. All the other companies requires X years in Y specific technology, even if you could deliver better than a candidate that has that experience, you will not pass the screening process.
Why is Creating a Learning Environment Essential for Technical Teams
Clearly is not essential, most of the tech teams I saw and know do not have such an environment. They provide access to learning resources, but there are only a few companies that have a learning culture.
It’s really important not to solve problems that have already been solved.
Yeah ... beside redundant internal tools like building, shipping and analytics, that many companies are building (dunno why), I even saw entire products that can be replaced by OSS versions. It is a shock for a dev working at one of this examples, for years, to find out that here is an OSS alternative out there. They just didn't searched.
maintaining the stability of your product
I dunno what exactly do you mean by stability, in a market or from a technical stand? If you strive for high SLAs and 0 bugs you will have to sacrifice delivering and feature adding speed, which in most cases, 99% of the business people will say no. Sounds good on paper, but impossible to achieve.
I am a connector of people at heart, personally and professionally. I love digging into the strategy of how to build and foster developer communities and have been doing so for 10+ years.
Thanks for taking the time to reply, Adrian! I completely agree that this doesn't apply to every company, but there are definitely a lot that are moving in this direction, both in the enterprise space as well as startups. I'm of course noticing it more in the San Francisco Bay Area, so that's a good portion of my sample set, but hopefully others in various locations will begin following the same trend.
Sometimes things that are actually essential for success don't exist... but if you look to the companies that are truly successful, not just riding a wave of popular tech tooling, they have indeed created a culture of learning. It might look different from place to place, but it exists!
re: stability, I mean availability of the product for customers -- uptime, etc. -- as well as continuing to solve problems for customers. I completely agree that there needs to be a balance between delivering features & fixing legacy code or problem areas. Some companies won't understand, but that's the value of metrics that show how much of a difference those fixes can make :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would so wish that the real world would function like this :( but we can only strive to do better.
I'm currently in the candidate role, in more EU countries, and I can tell you that it is only a fairy tale. It applies to huge corporations like Google. All the other companies requires X years in Y specific technology, even if you could deliver better than a candidate that has that experience, you will not pass the screening process.
Clearly is not essential, most of the tech teams I saw and know do not have such an environment. They provide access to learning resources, but there are only a few companies that have a learning culture.
Yeah ... beside redundant internal tools like building, shipping and analytics, that many companies are building (dunno why), I even saw entire products that can be replaced by OSS versions. It is a shock for a dev working at one of this examples, for years, to find out that here is an OSS alternative out there. They just didn't searched.
I dunno what exactly do you mean by stability, in a market or from a technical stand? If you strive for high SLAs and 0 bugs you will have to sacrifice delivering and feature adding speed, which in most cases, 99% of the business people will say no. Sounds good on paper, but impossible to achieve.
Thanks for taking the time to reply, Adrian! I completely agree that this doesn't apply to every company, but there are definitely a lot that are moving in this direction, both in the enterprise space as well as startups. I'm of course noticing it more in the San Francisco Bay Area, so that's a good portion of my sample set, but hopefully others in various locations will begin following the same trend.
Sometimes things that are actually essential for success don't exist... but if you look to the companies that are truly successful, not just riding a wave of popular tech tooling, they have indeed created a culture of learning. It might look different from place to place, but it exists!
re: stability, I mean availability of the product for customers -- uptime, etc. -- as well as continuing to solve problems for customers. I completely agree that there needs to be a balance between delivering features & fixing legacy code or problem areas. Some companies won't understand, but that's the value of metrics that show how much of a difference those fixes can make :)