It's the worst reason to end up there, because you have to really want to work there for some qualitative reason to have any hope of adapting to and succeeding in that culture. I always felt so bad when I helped onboard a new hire who said they just wanted to experience working at a FAANG.
IIRC water in earth's mantle is magnitudes greater than the volume contained in our oceans. I think only part of Earth's H2O story is illustrated by this graphic.
Most people don't directly query or otherwise operate on raw CSV, though. Large source datasets in CSV format still reign in many enterprises, but these are typically read into a dataframe, manipulated and stored as Parquet and the like, then operated upon by DuckDB, Polars, etc., or modeled (E.g. DBT) and pushed to an OLAP target.
There are folks who still directly query CSV formats in a data lake using a query engine like Athena or Spark or Redshift Spectrum — which ends up being much slower and consuming more resources than is necessary due to full table scans.
CSV is only good for append only.
But so is Parquet and if you can write Parquet from the get go, you save on storage as well has have a directly queryable column store from the start.
CSV still exists because of legacy data generating processes and dearth of Parquet familiarity among many software engineers. CSV is simple to generate and easy to troubleshoot without specialized tools (compared to Parquet which requires tools like Visidata). But you pay for it elsewhere.
I haven't thought about sqlite as a data interchange format, but I was looking at deploying sqlite as a data lake format some time ago, and found it wanting.
1. Dynamically typed (with type affinity) [1]. This causes problems with there are multiple data generating processes. The new sqlite has a STRICT table type that enforces types but only for the few basic types that it has.
2. Doesn't have a date/time type [1]. This is problematic because you can store dates as TEXT, REAL or INTEGER (it's up to the developer) and if you have sqlite files from > 1 source, date fields could be any of those types, and you have to convert between them.
3. Isn't columnar, so complex analytics at scale is not performant.
I guess one can use sqlite as a data interchange format, but it's not ideal.
One area sqlite does excel in is as a application file format [2] and that's where it is mostly used [3].
Yes. AWS enterprise support costs a minimum of USD 15k/month. You receive a dedicated TAM and account SA for more strategic projects or problems, as well as faster live-help response through the ticket system.
Yep. It's not noise on the MIDI signal, obviously, it's crosstalk induced by USB circuitry. It gets worse when bus power is involved; USB-powered instruments are notorious for it.
I like it, too, but the "What is this?" text should be displayed on the home page, not after clicking. It would assuage most of these types of concerns.
it is displayed (or at least it's supposed to be displayed) at the same time that the "enable webcam" button is[1] - if it's not that's definitely a bug! Are you on mobile? Would love to fix whatever you're seeing.
[1] they should both fade in as soon as the facial recognition stuff loads
Aliens are notoriously bad drivers. Have you seen those videos where they just hover in the sky and then zoom off? Homeboy's gonna catch an intergalactic DUI.
