havermeyer

Bank of America Unlimited Cash Rewards for the win :) My only regret is not realizing sooner that it existed since I used the Citi Double Cash card for so long.

It makes me think of the how "I have thirst" is the literal translation from the French for "I'm thirsty."

The Abseil time library makes time and date parsing and manipulation a lot nicer in C++: https://abseil.io/docs/cpp/guides/time

I reviewed a CL from Hyrum at Google where he was trying to remove a `set_timeout(float)` method in favor of `set_timeout(absl::Duration)` and changed the former to delegate to the latter. It turned out that there was some special handling of inf/nan in the legacy API, despite no mention in the documentation, and his CL broke a number of tests. It was amusing to experience Hyrum's law so directly :)

Something else to consider is compile time versus runtime validation with formatting libraries, e.g. due to passing the wrong number or type of arguments. The Abseil str_format library does compile time validation for both when possible: https://abseil.io/docs/cpp/guides/format

I wish I could find the article I read a while ago on the history, but it reminds me of how "nauseous" ended up becoming synonymous with "nauseated."

Sorry, I didn't check comments for a while. The target date funds tend to have higher management fees and yes, worse composition of stocks versus bonds compared to holding a mix yourself, IMO, based on your goals.

FYI you may be better off using an index fund and then rebalancing into bonds or other fixed income options closer to retirement. See this article, for example. https://www.cnbc.com/2018/07/13/one-of-the-biggest-retiremen...

That would also be interesting to analyze: which de facto attributes do people add because they think they're needed to pass an initial screening?

The C API for Julia also has almost no documentation. There is a getting started guide, which is great, but if you want to do anything more advanced (e.g. creating structs like in your example), you'll end up reading the source code to try to puzzle through which functions to use in julia.h. There's also an apparent limitation that whichever thread initializes Julia is the only one that can later eval code, which was surprising. The language itself is very cool, but it has a long way to go to be easy to embed like Python is.

There's even a subreddit dedicated to awful taste but great execution :) https://old.reddit.com/r/ATBGE/

Gordon is amazing, and it's almost impossible to beat him to an answer for certain types of questions :) I had the chance to meet him a few years back to talk through some new SQL features coming to BigQuery (I'm at Snowflake now). He had a lot of great insights into what could make the product better, and what he thought was missing relative to other OLAP databases.

Axios uses this format, where they have a short summary and bullet points. Here's an example: https://www.axios.com/tropical-storm-henri-slams-new-england...

Sharing since this sounds interesting but also like a terrible financial idea.

I hadn't heard about this mantra before:

Management's reasoning fell in line with CEO Mark Zuckerberg's early mantra, "company over country," according to the book.

"As a private global company, Facebook did not want to engage in geopolitical skirmishes, and it certainly didn't want to be in the middle of contentious national elections," the authors write. "Facebook was, above all, a business."

absl::StrFormat provides compile-time safety: https://abseil.io/docs/cpp/guides/format

Did you keep in touch with any of the other students? I can't imagine that anyone came away thinking it was pleasant, but I'm curious how their thoughts on the experience compared to yours.

I saw a lot of this when I worked at Google, both with internal-facing products and external-facing ones (software, though, not hardware). Organization A would build their own query engine, for example, but then organization B would build their own competing one because A's solution didn't quite work in the ways that they wanted it to. The result, of course, was that now you have a proliferation of query engines, and if you're a neutral party, you just end up being confused about which to pick since they all have tradeoffs, and none of them have sufficient headcount to build out more complete functionality. In terms of external products, there's a long line of competing chat, video calling, payment, etc. solutions, most of which have been killed off by now.

My takeaway was that I wish leadership had thought more critically about how to invest resources across organizations to build fewer but more adaptable products, but I don't think the right incentives existed :/

Archive link: http://archive.today/2021.05.08-195117/https://www.nytimes.c...

Context for anyone who missed the original thread on Twitter: https://twitter.com/skirani/status/1149302828420067328

As a disclaimer, I work on the BigQuery team, but I wanted to point out that there is now support for transferring data from S3 to BigQuery: https://cloud.google.com/bigquery/docs/s3-transfer-intro

Tables created in projects that have BI Engine enabled support streaming inserts, DML operations, etc. just like other BigQuery tables. Any queries you run using BigQuery itself incur regular query costs (https://cloud.google.com/bigquery/pricing#queries) but there are no extra charges beyond the storage costs (https://cloud.google.com/bi-engine/pricing) for BI Engine to manage the data for you behind the scenes.

Give BI Engine a try! https://cloud.google.com/bi-engine/docs/. The model is that you pay for storage--currently free during the beta--but any queries from Data Studio don't incur costs. It was just announced during Next this week.

As a disclaimer, I'm an engineer on the BigQuery team (but not BI Engine specifically).

I'm curious about the options that they'll offer initially. With the Model 3, Tesla only sold the long-range, premium version at first, which IIRC is more profitable than the basic $35k version. Maybe they'll repeat this with the Y and sell just a more expensive model first as well.

This recent article makes it sound like it can be a nightmare to get your money back, too: https://www.cnbc.com/amp/2019/02/21/tesla-refund-and-return-...

If the Remembrance of Earth's Past trilogy taught me anything, it's that keeping a low profile is the safest choice :) Highly recommended if you are into sci-fi.

This sounds like a terrible idea. You can provide a way for people to opt out of legacy behavior, but don't break them outright unless you want to lose your most faithful, long-term users.

I'm biased (I work on the BigQuery team) but I'm always excited to see more public datasets made available in BigQuery: https://cloud.google.com/bigquery/public-data/. It would be great to have government data available through a variety of cloud services with free exports.

Some personal favorites among BigQuery public datasets include NOAA GHCN[0], the Census Bureau's Zip Code Tabulation Area [1], and FEC Campaign Finance [2].

[0] https://console.cloud.google.com/marketplace/details/noaa-pu... [1] https://console.cloud.google.com/marketplace/details/bigquer... [2] https://console.cloud.google.com/marketplace/details/bigquer...

Thanks!