2,324 karma · joined September 21, 2020
We don't have superintelligence, we don't have the remote idea of how to get started on creating it, in all likelihood we don't even have the correct hardware for it or any idea what the correct hardware would look like. We also don't know whether it's achievable at all.
Isn't that just a result of everyone being into Spark a few years ago?
That's why you don't optimise for it in a vacuum. You weigh the potential benefits of switching to Haskell versus the additional cost of maintaining/growing a Haskell team.
Of course, there is just more of them in the first place. The other effects that you describe might also be true but keep in mind what the base rates are.
How is it easier to find a Haskell developer vs finding a Java/Python/PHP developer?
They rebranded in July 2020 - https://element.io/blog/welcome-to-element/
Some people say this, others say that it makes your daily work worse because going back to a language that isn't on the cult-approved list is so difficult.
This varies a lot depending on where you live, your skin color and your socioeconomic status.
What does correctness-sensitivity mean in this context and how is it missing from a language like Python for example?
Anyone who violates Twitter's terms and conditions.
That's interesting, I really didn't think that it's that common. In many companies this ranges from very difficult to completely impossible and certainly isn't just a formality. I guess that we have just been exposed to very different types of company/management.
You need to add 3 constraints to the question
1. What is your starting point and current knowledge of mathematics and statistics?
2. Minimum viable for what? What do you need the statistics knowledge for?
3. How much effort can you afford to put into this over what period of time?
Then the answer ranges from "here are a couple of good youtube videos" to "here is how to design your own degree in statistics using freely available material".
> ...they thought I should be using the S word!
The question suggests that you can somehow give yourself a new title which usually isn't true for people who work for someone else. Hopefully the titles that you put on your resume are your actual titles at the companies that you worked for, not something you came up with. Don't worry about calling yourself anything.
At the same time if you are able to get a promotion or apply for a senior role, that's great - go for it. It's nice that people around you are recognising your progress in some way.
Last thing, titles have meaning within any given company but are almost useless when comparing across companies. In some places to get a senior developer title, you just need to ask. Your manager then tells HR to change one cell in a spreadsheet and congrats - you're a senior software engineer. In other places you can become senior if you've been on a team for a year and everyone else has been there for a couple of months ("you have multiples of their experience, of course we can call you a senior engineer"). In those places you just need to be senior relative to the people around you. And in other companies it's a much more rigourous process with very specific criteria. There are people will decades of impressive high-profile engineering work at big companies whose title is just "Senior Software Engineer".
As you're pointing out, currencies don't have built-in inflation or deflation, that's why it didn't make sense to answer the exact question that the parent comment was asking.