91 karma · joined May 29, 2015
Anyway, excellent write from Mary Rose and she is an exceptional presenter as well!
In the future, those codebases will only be the legacy ones and you will end up doing more maintenance with C++.
With Rust your investment of today will pay off in a few years.
Deciding what to learn today is an investment decision and you should look into what you think the future will look like. To me it looks Rusty. :-)
I think there is a problem when we cancel ideas because of whom is telling them.
Most visits to doctors it is not about only about the sickness (or information about what medicine to get), but about socializing and somebody inspect you and discuss with you. This part, the machine cannot do. It is what is called the doctor-patient relationship. If you think this is not the important part, I cannot disagree more with you.
I go to doctors only when I really need, but the pattern I see around is that people have a real long lasting trust relationship with the doctors they see.
Again, thank you for putting this into a post!
Those two factors are a reality now a days: people leave teams when they get experience and go to a place where they have 0 experience (knowledge is lot) and they built everything under pressure to deliver to meet market demands (so we rush to deliver features).
I would also tell you that in the past well organized projects were exception not the rule.
”Often they have not even bothered to do basic troubleshooting, things like read the documentation on what the error message is attempting to tell you.”
This happens, but this just means that your Development Team needs some coaching or to improve their quality.
This tells more of a quality of the development team you have been working with. You have to pass along this feedback and ensure that Development team also works with professionalism as everybody else.
DevOps would tell be that "Dev & Ops" would look up issues together (Yes, he will be blocked as well WORKING with you), if you find that it was developer's fault. Tell them: "Hey, this is on your side. You saw how we troubleshooted together. Now each of us has new tricks to use in the future".
If you don't do that, you are the shortest path to get THEIR problem solved. And it is too easy to go that path.