I agree the economics here don’t make sense, but leave where? The rest of the world has increasingly strange, or at least unattractive, economics too.
The US is a difficult and long process to get a green card. Other English-speaking countries aren’t necessarily better: Australia seems similar in terms of being a natural resource extraction economy with insanely high real estate prices. Same productivity and salary concerns with the UK.
It's trivial to move to the USA on a TN1 from Canada compared to any other visa category.
If you have a job letter, you show up to the airport and CBP can issue it immediately.
This includes software development which is responsible for GDP growth. Which is why 80-90% of CS students at the University of Waterloo immediately move to the USA after graduation.
There is no tech talent in Canada due to the pay/tax difference and TN1 is good for SWEs.
e.g. Nobody at my office has heard of Gas Town yet. I had to get an invite to a predominantly American Teams chat to discuss it. It's a very draining environment.
Also, senior devs make US$110k and a detached home costs US$800k. I would pay less in taxes and a home would be cheaper relative to income in California.
The "there is no tech talent in Canada" folks have their heads buried in the sand. Markham is a tech hub, and so are a bunch of other places. Obviously it doesn't have the scale of the Bay Area, and the salaries are indeed lower than the Bay Area.
Many of us choose to live in Canada for a variety of reasons, and it is not because we couldn't get a job down south. Some of us even had to turn down moving to the US multiple times in our careers, but that idea is uncomfortable for some folks. It is almost as if some people value other things in addition to money.
If I could, I wouldn't. The U.S is fine usually to visit, but I wouldn't prefer to live there. Thankfully there are theoretically other alternatives that are much more appealing regardless of absolute earnings. The vibes could be better north of the border, but the U.S gives the ick
Apart from network latency, one of the behaviours I've seen with Redis is that reads/write latencies are fairly linearly proportional to the amount of keys queried - which seems to be shown in your chart as well.
We had a different problem, where our monolithic app used both Postgres / Redis for different use cases and worked relatively well. However - it was a lot easier to shove new functionality in the shared Redis cluster. Because Redis is single-threaded, one inconsiderate feature that does bulk reads (100K+ keys) may start to slow down other things. One of the guidelines I proposed was that Redis is really good when we're reading/writing a key, or small fixed-cardinality set of keys at a time, because we have a lot of random things using Redis (things like locks and rate limits on popular endpoints, etc).
However, in your case, I'm guessing Redis shines in the case of a naive single-key (IP address) lookup, but also doesn't do well with more complicated reads (representing your range query representation?). Cool write up overall, I don't have a deeper understanding of how SQLite performs so well when compared to a local Redis instance, so that was unexpected and interesting to observe.
My experience with Redis is similar, where it often becomes a trap because people misunderstand it's strengths and weaknesses.
I think it's best to consider Redis a cache with richer primitives. It excels at this and used appropriately will be both fast and solid.
But then people start wanting to use it for things that don't fit into the primary rdbms. Soon you have a job queue, locks of various sorts, etc. And then it just becomes a matter of time until performance crosses a cliff, or the thing falls down for some other reason, and you're left with a pretty ugly mess to restore things, usually resulting in just accepting some data loss.
It takes some discipline to avoid this, because it happens easily by increments.
As for SQLite's performance, besides avoiding network overhead, a lot of people underestimate serialization and deserialization costs. Even though Redis uses a pretty minimalist protocol it adds up. With SQLite a lot of things boil down to an in process memcopy.
I’m constantly astonished “Thinking Fast and Slow” is so highly recommended - I question if the advocates actually read the book in depth.
I remember reading most of the book and skipping a couple of chapters. While the results and ideas are great, I feel most of the chapter is the historical background, Ie “Tversky and I were doing this in the 60s …” It could be heavily reduced and still get the point across.
Despite your name referencing insanity I love your comment and it's a beacon of rationality in the current tech interview bubble. So generally I agree, but unfortunately sometimes the format and expectations of the coding interviews really demand prior grinding. I don't like it but it's the reality.
IE let's say you have a graph question that requires either BFS and DFS. You're a competent engineer who both recognizes the applicable algorithm and could reasonably implement it from scratch.
Some problems then have additional constraints such as adding bounds-checking (if searching inside some sort of "map") and checking visited nodes. The engineers who've grinded leetcode have muscle memory ready to regurgitate code for those conditions.
Competent engineers are able recognize these and implement them, but that lack of muscle memory wastes vital time for the interview. (Yes, those seconds are never a real constraint in the day-to-day).
I have started a petition to restrict Russia's access to American cloud infrastructure. Existing sanctions against Russia don't go far enough symbolically, nor economically, to account for the massive devastation they have inflicted on Ukraine.
My petition requests US political and cloud business leaders to remove their services from the Russian market.
The following is a non-exhaustive list of which companies I'd like to stop offering services to Russia:
- AWS, Microsoft Azure, Google Cloud Platform
- IBM Cloud, Oracle, Rackspace
- Cloudflare, Akamai, Fastly
- Cisco, Juniper, F5, Palo Alto Networks
Today I just want to get at least 100 signature on the petition.
Starting next week, I'll reach out to my network to find people who work at these companies to
share this message with leadership.
I work there currently and I agree - I can imagine frustration for a while after leaving and not having a good place to make a bunch of posts.
Posts and work groups are actually a generally good way for scalable work communication - and leaving a public and searchable record. This doesn't replace Google docs and wikis, but serve as another layer to organize them. (I promise this doesn't lead to needless bureaucracy, that still happens but not because of Workplace).
I have seen no indication of system design documents falling out fashion. If anything, the problem is the initial, pure document is used as a reference for too long instead of proper up-to-date documentation.
I'm currently putting together a design document (very simple system and still high-level) to ensure my idea is communicated concisely and unambiguously.
The main motivation is I'll have a refined reference to point people to so I don't have to worry about repeating context to all possible stakeholders.
I found this book because I just finished playing Dishonored 2 and I wanted to read a book with a dystopian steampunk alternative-Victorian vibe.
The events take place in a gritty, corrupt city of waterways and canals controlled by different factions. The factions represent either the legitimate nobility or the extensive underground criminal empire. A charismatic leader of a small young group of thieves and pickpockets comes up with an epic, layered con that will break sacred agreements and make him enemies with everyone - and pulls it off.
I found this disappointing - the moral position made no sense and that disconnected me from the characters. I enjoyed Low Town: The Straight Razor Cure a lot more in the same vein.
I just read this recently also, and I agree it’s a great book. “dystopian steampunk alternative-Victorian vibe” describes it well - it’s a society with advanced chemistry and materials (“elderglass”), but no gasoline, electricity, computers, etc.
The US is a difficult and long process to get a green card. Other English-speaking countries aren’t necessarily better: Australia seems similar in terms of being a natural resource extraction economy with insanely high real estate prices. Same productivity and salary concerns with the UK.