Depends on what you see as “the job”. I would prefer many projects to be better than they currently are, both from the end user and the developer side.
When I think about the projects I have seen, you need very good people to clean up technical debt in a viable and sustainable way, as well as develop in a way that is sustainable and maintainable in a good way long term.
If you don’t have very good people, code quality devolves quickly, whereas the negative impact is felt a bit later, and at that point, it’ll be hard for most people to clean up and improve the project in a reasonable fashion, and it usually never happens.
The skill, experience, and being able to grasp what needs to be grasped gap is one thing, the time people are in a project or firm is another.
In the end, it depends on what the job is. Sure, most apps work. But there are so many applications that annoy and hinder me as a user. Even as a user, it’s a mess. I’m sure the dev team doesn’t have it much better on those projects.
With very good people acting as mentors and guidance, others can certainly get the job done, and contribute in productive ways. Most importantly, they learn and improve significantly.
I guess overall it’s not really about the big gap, but more of a continuum of skill. There’s certainly a weighted spread though.
You went on though to describe how difficult and technical the skill is needed to wade through this code. Which is kind of in my mind what I’ve seen with so many jobs. People in roles for long periods of time have this ability to make their job seem like the most difficult thing possible. Lately I’ve been watching these window tinting competitions. Listening to those guys describe putting on window tint always reminds me of tech guys. It’s like at some point just chill out. It isn’t that important.
Depends on what you see as “the job”. I would prefer many projects to be better than they currently are, both from the end user and the developer side.
When I think about the projects I have seen, you need very good people to clean up technical debt in a viable and sustainable way, as well as develop in a way that is sustainable and maintainable in a good way long term.
If you don’t have very good people, code quality devolves quickly, whereas the negative impact is felt a bit later, and at that point, it’ll be hard for most people to clean up and improve the project in a reasonable fashion, and it usually never happens.
The skill, experience, and being able to grasp what needs to be grasped gap is one thing, the time people are in a project or firm is another.
In the end, it depends on what the job is. Sure, most apps work. But there are so many applications that annoy and hinder me as a user. Even as a user, it’s a mess. I’m sure the dev team doesn’t have it much better on those projects.
With very good people acting as mentors and guidance, others can certainly get the job done, and contribute in productive ways. Most importantly, they learn and improve significantly.
I guess overall it’s not really about the big gap, but more of a continuum of skill. There’s certainly a weighted spread though.
I don’t think you answered the question.
You went on though to describe how difficult and technical the skill is needed to wade through this code. Which is kind of in my mind what I’ve seen with so many jobs. People in roles for long periods of time have this ability to make their job seem like the most difficult thing possible. Lately I’ve been watching these window tinting competitions. Listening to those guys describe putting on window tint always reminds me of tech guys. It’s like at some point just chill out. It isn’t that important.