This repository contains dumps of the monthly Chrome UX Report (CrUX) datasets.
Dumps are automatically generated by exporting URL and rank columns from the CrUX dataset via BigQuery, grouping URLs by rank, and storing the grouped URLs as XZ compressed archives. This repository is intended as a convenient alternative access, since exporting the data from Google BigQuery is both cumbersome and expensive.
The latest dataset (from March 2023) contains more than 18 million websites.
Note: There is no unique rank assigned to websites in CrUX datasets. Instead, they are grouped into buckets of similar ranks.
This repository contains dumps of the monthly Chrome UX Report (CrUX) datasets.
Dumps are automatically generated by exporting URL and rank columns from the CrUX dataset via BigQuery, grouping URLs by rank, and storing the grouped URLs as XZ compressed archives. This repository is intended as a convenient alternative access, since exporting the data from Google BigQuery is both cumbersome and expensive.
The latest dataset contains more than 18 million websites.
Let's assume just for a second that copyright violation isn't a problem, that 1B is enough to motivate enough people, that it's not overrun by bots, etc..
What kind of blockchain would actually be able to deal with the expected transaction count? According to [1] Ethereum peaks out at 15 transactions per second, but [2] claims around 6.000 tweets per second on average.
A difference of 2–3 orders of magnitude is not something a team of 5 engineers can simply solve in 6 months.
Radio.net is a leading audio platform that allows you to listen to 40.000 internet radio stations and over a million podcasts in your browser or through our iOS and Android apps — but we're also integrated with car multimedia systems and third-party devices like Sonos.
The current backend team of 3 is looking for an experienced engineer who's excited to help build the next generation of our APIs and services. Our tech stack is built on Golang, Postgres, Redis, DynamoDB, and Elasticsearch running on AWS' Fargate and Lambda via Terraform. We embrace the "you build it, you run it" principle by owning all operational responsibilities.
Radio.net is a leading audio platform that allows you to listen to 40.000 internet radio stations and over a million podcasts in your browser or through our iOS and Android apps — but we're also integrated with car multimedia systems and third-party devices like Sonos.
The current backend team of 3 is looking for an experienced engineer who's excited to help build the next generation of our APIs and services. Our tech stack is built on Golang, Postgres, Redis, DynamoDB, and Elasticsearch running on AWS' Fargate and Lambda via Terraform. We embrace the "you build it, you run it" principle by owning all operational responsibilities.
I think this is too harsh. A company can establish an enjoyable and empowering culture, that attracts and supports talented developers — and can still try to avoid hiring obstacles at the same time. It might not have been what therealmarv meant in his post, but your comment makes it sound mutually exclusive.
As a counter-argument: I've experienced several times that "niche tech" companies offered non-competitive salary packages and perks, because they offered the cool tech instead; "sure, we can't match that other offer, but we built our stack on that language/tech that is so hot right now".
Not arguing about the quality of Elixir, just about the gatekeeping that happens in this thread.
I have never used Elixir, so maybe it's a great language, maybe not. But I have to question the reasoning of the post simply going by the comments about other languages in the "Conclusions" sections — some of which I did use extensively.
Really, Go "is the choice if you need to 'sell it' to a 'Boss'" and the imperative programming style leads to more complexity? And Python/Django can only be used if you "don't need anything 'real time' and just want RESTful 'CRUD'".
I get it, you guys like Elixir, but painting the world using such broad strokes doesn't really sound like "kaizen learning culture" to me, but more like "Negative Nancy".
These are all good tips, but I want to stress the importance of (6). Much of what the original post is talking about can be improved by adopting the habit of making small, incremental changes. As the author, you no longer have to wait "in the order of weeks" for the feedback and a potential rebase should pose little risk. As the reviewer, you don't have as much mental burden and most reviews can be done "in-between" bigger tasks, e.g. in the 15 minutes before a meeting or before lunch, etc.
As for 1) I highly recommend to automate that away as much as possible. A strict syntax guideline and a toolchain that enforces it will go a long way.
That's simply not true! I'm 43, and there hasn't been a day without coding since I got my first computer 32 years ago. I'm also managing teams for the last 20 odd years; small teams, large teams, in startups and large corporations. And I know many others like me.
I understand that some aspects of a Hackathon might be fun, but nowadays my time is simply more valuable than that. Spending time with my loved ones, taking care of myself, putting in a few hours on a pet project that I don't plan to throw away in a few days, and even going to an event for some proper networking feels a much better use of my time than a Hackathon.
Dumps are automatically generated by exporting URL and rank columns from the CrUX dataset via BigQuery, grouping URLs by rank, and storing the grouped URLs as XZ compressed archives. This repository is intended as a convenient alternative access, since exporting the data from Google BigQuery is both cumbersome and expensive.
The latest dataset (from March 2023) contains more than 18 million websites.
Note: There is no unique rank assigned to websites in CrUX datasets. Instead, they are grouped into buckets of similar ranks.