We use a pattern where we ETL things into tables that model the upstream source closely, then use SQL Views to tighten up the model and integrate across data sources where needed. Keeping this all inside one DB allows us to use tools that understand the schema for autocomplete, etc.
I expect the developer experience would be significantly worse if we started writing views in YAML instead of SQL… but you’ve found the opposite?
Yes. This is the killer app for blockchain. I want Movies Anywhere, but for everything and without an industry gatekeeper. If I am subscribed to Netflix, I should be able to watch every video in their catalog through any service that has the bits.
Yes. Once I was leaving a managerial role for a lateral transfer and helped choose my replacement. One candidate was a high performing individual contributor. They felt obligated to apply for the job, but didn't really want it. They liked their current job and did it well. They were assured that they're welcome to continue as an IC at their current level as long as they continue to perform at their current level.
Worked out great. They have their role and continue to enjoy it and perform well. The managerial role went to someone with clear upward intention, who is also enjoying it and performing well.
I was recently struggling to model a financial process and solved it with Units. Once I started talking about colors of money as units, it became much easier to reason about which operations were valid.
TIL that steam distribution was invented in the USA around 1880, and is still used in NYC. Never occurred to me that “Steam Plants” literally produce steam for distribution. I thought that was a glib reference to the white smoke they produce!
Yeah. If people are worried enough about something that they vote this hard about it, go ahead and do some more tests. Be super transparent.
The real fight will be the communications about the results. Bend over backwards to explain everything extremely clearly. If RFK Jr oversees a milestone study that dramatically shows there is no vaccine/austism connection then maybe, just maybe, we can stop talking about it.
Then again, flat earthers seem to lose faith in their experiments as soon as the results disagree with their preferred outcome…
I'd be more worried the results are something like "1% chance of saving your life and 0.001% chance of exacerbating autism symptoms" and RFK focuses entirely on the latter as an excuse to ban vaccines.
We know vaccines can have negative side effects, but a reasonable person weighs those against the (larger) benefits. I don't think the current regime is very reasonable though.
That’s a proximate-cause analysis. If the root of their problem is a rangefinder, what happened that caused them to consistently miss with it?
The lack of credible comments strikes me as someone socking the answer: they’ve committed to a stacked format that is inherently unstable. If they can’t get an answer out before the next budget is passed, their contracts should be cancelled.
They propose to address this with a buck regulator:
> [If] we are to get rid of galvanic isolation [there's still a ] need to prevent mismatches between the utility’s AC line voltage and that of the EV battery.
> The solution to this problem is a device called a buck regulator (or buck converter). A buck regulator is similar, functionally, to a step-down transformer, except that it handles DC current rather than AC. In the event that the utility’s AC voltage exceeds the battery voltage, the buck regulator operates like a transformer and steps it down. In comparison with an isolation link of the same power rating, a buck regulator would cost less than 10 percent and the power loss would be less than 20 percent.
We use a pattern where we ETL things into tables that model the upstream source closely, then use SQL Views to tighten up the model and integrate across data sources where needed. Keeping this all inside one DB allows us to use tools that understand the schema for autocomplete, etc.
I expect the developer experience would be significantly worse if we started writing views in YAML instead of SQL… but you’ve found the opposite?
reply