mping

Pico? Not nano? Hah you're old :)

I was thinking more like CPUs and GPUs

Besides, in tech, most of the time you get what you payed for. So if you lowball you will probably get low talent.

This is a global market, so you can also grab US jobs for half the pay and make alot of money anyway.

There are some fintechs already paving the way and abstracting psd2 away. I just tried to log into my bank using tink (no affiliation) and it worked great.

I believe that in db context, vectorization means batch processing column wise. Quoting the CockroachDB blog post:

Using vectorized processing in an execution engine makes more efficient use of modern CPUs by changing the data orientation (from rows to columns) to get more out of the CPU cache and deep instruction pipelines by operating on batches of data at a time.

Here is the link: https://www.cockroachlabs.com/blog/how-we-built-a-vectorized...

You can also tap shift a couple of times and a pop-up appears with all possible options (a superset of cmd shift a)

It also means jack in Austria I guess :) honest mistake

Metosin stuff is really nice too (compojure-api, malli, reitit). And while we are at it, ztellman's aleph and manifold are sweet too.

I generally agree with your statement, otoh I have used some libs that are not being actively maintained for years and they still work, out of the box.

Clojure strength is its weakness. But yes, there is a long way to make it more beginner friendly

Also, it seems that Raft is easier to understand and implement, according to some papers and blog posts I skimmed.

Thanks for your work in webtorrent!

But on these processors, I believe the frequency is rarely sustained right? Due to thermal throttling and other factors.

I'm wondering did anyone actually tried it? It's not impossible for an automated tool to give valuable feedback over a PR guys. Should be easier than a self driving car I guess

I prefer dotfiles too, I recently built a new machine and was able to configure most of stuff just by using dotfiles.

By carefully managing scripts (mostly .zshrc) I can even use the same dotfiles between mac and linux.

For me there are two big contributors to flow (and flow may not be the same for everyone): requirements are very well understood and willingness to code the requirements.

If it's boring or boilerplate it doesn't work. Otherwise, some kind of flow normally happens. I believe you require some amount of concentration hence the need to not be interrupted, and it has to be a bit challenging to require concentration.

An example would be an interview or college exam: you are pressured and needed to stay focused, yet the time passed very quickly.

Article is thin but had loads of links. It's more of a compendium than an article.

I completely agree that microservices are more organizational related than tech related.

Netflix is a good comparison because google will need to secure rights for AAA games, and some games don't appear in all platforms.

Fortunately, a user can install Steam/GOG/Origin whatever and just pay for a single game, unlike video streaming platforms.

In terms of pricing, 9$99 for 4K/60Hz games is 120$/y; if you buy two AAA games (around 59$) it's already the same price, so in the end the appeal is NOT having a beefy computer to play whatever game you'd like. My guess is that hardcore games will have their own PCs, console gamers prefer TVs but the "casual" gamer may be attracted depending on the catalog of games.

edit: it seems you have to buy most of the games too? So google is basically renting a gaming PC with a higher latency.

First google hit: https://www.yugabyte.com/yugabyte-db-vs-cockroachdb/ My understanding is that CDB is a bit more focused on correctness before focusing on performance.

I'm guessing the creators solved a real business need and decided to go open source. Really nice folks btw. Props to juxt.

I'd just like to add that is easier to compare candidates using algorithm challenges (you can check if the candidate reached the optimal solution, how long it took and so on).

I dislike this kind of interviewing because you miss the chance of hiring people that are different from your regular hires, but hey the FAANGs are doing great so who am I to criticize.

Dns resolver Internal IPs

Thanks for the detailed account. Most of the stuff you mentioned can be totally fixed with a shift of perspective. In fact, as long as you compare with your peers you will feel somewhat unhappy. I'm pretty sure lots of people at FAANGs feel like getting by in comparison to some one else who apparently is better off. There's a lot of people in the world who would kill to have your problems though.

As for more practical, you can move to a city with lower CoL, get a job at a FAANG, hire a fulltime nanny (find other couple(s), 2k/month x2 is 48k/year, shouldn't be hard) to take care of the kids at someone's place.

Sweet, didn't know about nchan too.

Yeah, we used nginx-push-stream-module[1] to support 1M connections with lower boxes. Websocket-as-a-service. Really cool module. Was a realtime project for a live TV contest where people could participate with their phones.

[1] https://github.com/wandenberg/nginx-push-stream-module

I'm pretty sure colocation is cheaper if you know what you're doing (what to buy, where to colocate, what kind of bandwidth required, etc). I'm also pretty sure a good portion of cloud customers don't know or don't want to risk it.

Yeah until it comes back and bites you in the a$$. Even toy projects take longer than supposed because we devs think it's a one time thing only. My experience is most of the time software lasts much longer than expected.

One use case is API input validation.

Java has a pauseless GC called Shenandoah, and Zing JVM from Azul systems also has pauseless ZGC (I believe Zing implemented it first). What most people don't realize is that eg. Shenandoah can slow down the allocation rate to keep GC in the time budget.

I think people prefer C and C++ because they can control the memory layout of the app, and specially in console games they can do much more low-level optimisations than using a higher level language. Besides, I'm guessing the pain in C++ doesn't come from memory allocation, you probably follow a well defined ruleset for freeing objects and you know you will be OK.

We're not tigers or bears, so I never really understood this line of thought.

Well, someone has to fix the mess we created, since it will persist long after we parents are gone.