> I’m hesitant towards C++ as it seems an ancient programming language and I don’t know for how long it will be around.
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.
Sometimes I get shocked by these numbers and it reminds me how little I know about business. Like if you showed me the wikipedia page for Zapier and asked me give it some value, I would be way off. Or if you pitched the business idea to me, I would tell you do something better with your time.
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.
This has been my limited experience with everything related to Emacs - fragmented tutorials on how to do x that work with someone's specific setup. And when you start looking around for fixes you get solutions for "this is how I do this with Prelude", "this is built-in", "my customized Spacemacs setup..." and at that point I throw my hands in the air, admit to myself that I'm not a real man and go back to VSCode.
Is it just bitter people who missed out on making a lot of money? Or is it sober and relatively informed people who are assessing Bitcoin correctly? How do we tell the difference between the two?
Seriously, what are the possible outcomes (positive or negative) that we can see play out? By what mechanisms can the currently inflated markets end and how will that impact the rest of the economy?
> It’s still not clear to me a person of this cadre need a PhD in a technical field in this day and age; they might contribute just as much faster if they chose any other route.
They might be able to contribute technically but they might not be given the opportunity to do so if they don't have a PhD.
> R is arguably easier for someone with little coding experience to learn, but Julia isn't that much more difficult, and it's much more intuitive to code in than Python.
Having some experience with all three of these languages, I find Julia much harder than R and less intuitive than Python. The relatively clean syntax isn't enough to make Julia an easy language.
Is the post only based on TIOBE? The same index that currently ranks JavaScript below Visual Basic and SQL below Assembly? That ranking is off by so much that anyone who takes it seriously loses at lot of credibility from the start.
I'm not entirely on board with the Julia hype train but they certainly got some things right and both the ecosystem and the community are healthy and growing. Julia doesn't need to replace a bunch of other languages immediately to be successful. Implying that the language is dead by using the word post-mortem is just demonstrably false.
You can although the specifics depend a lot on what you're swtiching from. A mechnical engineer, an accountant, a history teacher and a blue-collar worker will need to approach this in very different ways.
And you can also freeze when you should fight. With only 1 or 2 all-nighters to pull off before finishing my degree, I just froze and couldn't write a single word. I would stare at the screen not being able to type even one more character for those reports. Ended up submitting the incomplete versions knowing that they aren't good enough for a pass.
That's how I droppped out of university with only two days to go.
People have been doing stuff like this for a long time - trading cards, the kid who was selling pixels on a web page (https://en.wikipedia.org/wiki/The_Million_Dollar_Homepage), astronauts were taking items in their personal kits with the intent to resell them later for high value etc.
I suppose that we'll see things like these get more weaponised as people look for easy ways to make money. I'm not interested in participating.
> is it a terrible idea to hedge that crypto is better or as good as gold during crisis?
Cryptocurrencies are still too volatile and untested. Maybe Bitcoin behaves like gold during a crisis, or maybe it's everyone's play money and when times get tough everyone will sell their Bitcoin first. We just don't have historical precedent for it.
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.