> I don't know what they do beyond cancelling accounts.
Unless they've got sophisticated with payment URLs, I don't think they couldn't do that on this alone. These kinds of spams would quickly become a DOS attack on other people's accounts, and some spammers could even be planning to get a refund from a wallet holder they only presume to be gullible.
Q: Who should file a complaint with the Internet Crime Complaint Center (IC3)?
You may file a complaint with the IC3 if you believe you have been the victim of an Internet crime or if you want to file on behalf of another person you believe has been such a victim.
Since I haven't been a victim, I don't think I can make a report.
Is this any better these days? I got scammed by someone out of $1600 and I knew their name and address, FBI never even bothered to respond. It’s been 15 years.
Personally, I just don't enjoy writing Elm and much prefer TypeScript. For me, TS is great because of the community, tooling, and its self-documenting nature.
It's great for keeping status quo, anything is great if it's already there. Community and tooling is the result of that, things that exist for a while. But if we want to move forward, advancing tech, TS is just ok-ish (at some point it's not though)
They "underpay" compared to Google, etc and compared to the Bay. But Shopify is a Canadian company first (I'm in the US) and they pay me a salary well over the average for my area (double), not much less than what I was offered by other remote companies (within ~$10k) but pushed north of $200k/yr by adding stock.
We also recently received info on a new pay structure that basically lets us choose how much of our TC is $$$ and how much is stock. We're excited and people will be given raises. There are news articles you can read online.
Shopify also aims to be a "100 year" company. It means not paying in the top 10, but also not overworking employees or firing the bottom 10% every year.
As someone who isn't in the Bay... they pay just fine for new hires and for tenured employees once they finish raises.
I wonder if the job-hoppers in the bay area will realise before it is too late that they are participating in a bubble that will undoubtedly collapse (happening now maybe...), leaving them shocked at their inability to demand +20% per new job...
“Have you tried turning off and on again?” is advice to perform a total state reset, which works because the system’s state is inconsistent but its sources of truth are not.
You never have to reset state if you do not have it in the first place. You get other bugs still, but you don't have the most common class of bugs.
But, you need some state. You just want to discourage it. Some of it can come from laziness, but with difficulty. (Chris Okasaki’s Purely Functional Data Structures uses it to de-amortize the bound on a FIFO queue.) Other things, like ring buffers, are harder to argue.
So you want to be able to express an array of IORefs, say, for your ring buffer. But the people who use it become aware that it is a stateful construct and must be used that way.
Read “what color is your function?” for a counterpoint, of course.
You do it if you're using a language where there's a rule that there are only functions. For example there's no concept of doing one thing followed by another. The only way you can arrange that is to have two functions and compose them: g(f(x)). So now you know that the code in g is executed after the code in f. Monadic composition is basically about doing that while having code that looks like it would in a regular language that has statements and sequential execution. There are a few other reasons, such as you can create your own control flow as-code, lifting, etc. But the primary driver is: because you can't write useful programs in a pure functional language without this trick.
Referential transparency, as the original post says. For example, in a functional language you're always allowed to transform
a = f()
b = f()
c = g(a, b)
into
a = f()
c = g(a, a)
because f() is guaranteed not to have side effects. (If it does return side effects through the IO monad, instead of actually performing the side effects, g receives two data structures that encode what IO operations to perform.) In an imperative/procedural language, f() may have side effects, and if it does the two programs are not equivalent.
This may (not) make programs easier to reason about.
And that's a company's prerogative. But in the US, that mentality can cause you to miss out on great contributors.
For example, if you are building a new e-commerce platform and can hire someone with 1.5 years of experience shipping a successful project at Shopify, you should do that. They will give you more than someone chipping away at a non e-commerce SaaS for a half dozen years.
Point is, context is key. But I can't speak to outside of the US.
I worked for a consultancy when covid started. They decreased salaries in case the economy tanked. They also started recruiting in cheaper places like Colombia.
Low and behold, salaries were never brought back to pre-pandemic levels.
