superbcarrot
Joined 5 years ago
Karma
1,079
Submissions
264
Member since
Jan 11
Joined 5 years ago
This might be your answer. She can look for ways to transition to being a cloud engineer. There is a lot of complexity there and plenty of work to be done for the foreseeable future. As a DBA she should find that switch easier to make than moving to data science.
How did you go about meeting people in the first place?
It will be around for a long time. This shouldn't be a reason not to pick up C++.
> I‘m currently part of a team that needs help with C++ development.
That might be a good sign that you should pick it up but the details matter a lot. Getting to the point where you're productive with C++ in an existing codebase takes a while even for people who are experienced with the language let alone someone who is just learning it. So I would invest the time to learn C++ for work only if it's a long-term project where you'll have the necessary support from the rest of the team and from your engineering management. You need to establish the expectation that you can't just jump in and immediately make meaningful contributions. If it's a case of "this old C++ repo runs a critical piece of our product and we need a person to make some changes and maintain it", then stay as far away as possible.