3 ms·

This is absolutely what happened in most cases. Once they quit programming back in the 2000 and they did not learn the newer techniques, they're out of touch.

This is absolutely what happened in most cases. Once they quit programming back in the 2000 and they did not learn the newer techniques, they're out of touch. A simple example would be when it comes to test automation. Back in the 2000, automating GUI tests with _high_ coverage might be acceptable. Fast forward to today, we all learned that there is a very high cost on end-to-end functional testing that involves complex UI so we tend to write 10% of UI test automation, 20-30% of integration tests, and the rest falls into the unit-testing bucket. That's just the tip of the iceberg. Other areas of improvement ever since: dealing with build, dealing with continuous integration, continuous deployment, source control, etc.

bowlofpetunias 13y ago
You really believe that programming is such a unique area that people cannot be fully aware of such developments without actually practicing them? Gimme a break. I'm aware of Coffeescript, Backbone, Angular e.a., and I never did one inch of javascript or front-end coding in my life. Hell, the last time I did anything on the client side we were still doing laying with tables and one pixel transparent gifs... Just because it says "manager" on my business card doesn't mean I had my head stuck up my arse since. It may no longer be my job to do, but it's still my job to know.
- edwinnathaniel 13y ago
  I specifically mentioned "if they did not learn new techniques". By learning, I'm referring to reading, go through some of the examples a little bit, but does not necessary practice the tools. I'm merely agreeing with the parent that there are cases where managers stop reading the tech side and focus solely on the management aspect (risk management vs JS frameworks). If the manager still hold on the traditional approaches, he/she would insist to have more UI test automation as opposed to spend time and invest more on unit-test.
vezzy-fnord 13y ago
dealing with build, dealing with continuous integration, continuous deployment, source control, etc. It's not like build systems and source control were invented after 2000. Or basic CI/CD practices for that matter (though perhaps not as automated as today). However, in the case of build systems, they have been reinvented a dozen times annually since then (mostly make clones).

bowlofpetunias 13y ago

You really believe that programming is such a unique area that people cannot be fully aware of such developments without actually practicing them? Gimme a break. I'm aware of Coffeescript, Backbone, Angular e.a., and I never did one inch of javascript or front-end coding in my life. Hell, the last time I did anything on the client side we were still doing laying with tables and one pixel transparent gifs... Just because it says "manager" on my business card doesn't mean I had my head stuck up my arse since. It may no longer be my job to do, but it's still my job to know.

edwinnathaniel 13y ago
I specifically mentioned "if they did not learn new techniques". By learning, I'm referring to reading, go through some of the examples a little bit, but does not necessary practice the tools. I'm merely agreeing with the parent that there are cases where managers stop reading the tech side and focus solely on the management aspect (risk management vs JS frameworks). If the manager still hold on the traditional approaches, he/she would insist to have more UI test automation as opposed to spend time and invest more on unit-test.

vezzy-fnord 13y ago

dealing with build, dealing with continuous integration, continuous deployment, source control, etc. It's not like build systems and source control were invented after 2000. Or basic CI/CD practices for that matter (though perhaps not as automated as today). However, in the case of build systems, they have been reinvented a dozen times annually since then (mostly make clones).