Yeah, there are a lot of more affordably priced solutions out there, but they still need a subpanel or similar cutover switch to be installed and that's where a lot of the electrician's cost is. Plus, the inexpensive ones like this $3300 Ecoflow are 120VAC (up to 3600W), so if you want to be able to power larger household loads like an oven or heat pump, you need to buy two (or more) of them (or a bigger unit), which doubles the price and gets you into the price ranger of other whole-house systems like a Powerwall or Enphase.
With the 120VAC unit, about all I could power in my house is lights, TV's, and maybe some small kitchen appliances, which limits how much power I could shift off of peak, maybe a KWh or two, which makes it harder to get any payback on the investment.
Unless the spread between peak/offpeak power prices becomes larger, I'm not sure that battery storage is going to be a worthwhile investment (for me). Or maybe if the utility bought back power at a reasonable rate during peak periods as the other poster's power company does...But the California PUC doesn't seem to be interested in incentivizing that model.
You and the article author sound similar actually, just at different poles. Author doesn't bring up much other than saying that Musk isn't hardcore leftist and is kind of mean, therefore he's a nazi. You are along the same lines, that "with us or against us" attitude characteristic of extremely online types.
I see. Would it be fair to say you treat it almost like Pandas, except that it has a lower memory footprint since data is written to disk instead of memory. IE you use it for on the fly analysis of large frames of data, not like more traditional database/datawarehouse?
BTW, your questions are exactly those that I've been ask over the last few months, but also with a lot of focus over the last few days. Still learning as much as I can so the following might not be true.
For what it's worth, there's a difference between using duckdb to query a set of files vs loading a bunch of files in to a table. But once the data has been loaded into a table it can be backed up as a duckdb db file.
Therefore it might be more performant to preprocess duckdb db files (perhaps a process that works in conjunction with whatever manages your external tables) and load these db files into duckdb as needed (on the fly analysis) instead of loading datafiles into duckdb, transforming and CTAS every time.
Unfortunately not. At least not without a little intervention. See this blog post for more details about what I mean. They inspect the iceberg table's catalogue to list the related parquet files and then load them into duckdb.
In the big picture, FAANG salaries are outliers. Boom and bust cycles come and go, and when it is booming again - circumstances can have changed.
I worked with people in oil and gas that never came back, probably making only 25%-50% of what did they did during their best years.
Finance, too. Lots of young bankers were forced out back in 08-09, and never returned.
(With that said, tech is a bit more flexible on hiring, and I don’t think a 350k engineer will have to take a 300k pay cut, finding a “normal” ~100k engineering job is very possible. Or even another FAANG job if you’re willing to keep going at it. Could take weeks, months, even years - depending on how bad the market is)
Depends on the quality of the developers you're looking to hire.
The market for the kinds of developers that command ~$350-500k is still incredibly tight. There's a reason that even though Stripe is reducing headcount by 14% engineers are mostly unaffected.
