surrealize

I gave a standing directive to my coordinator to process subagent transcripts (with a simple Claude-written script that reads the transcript .jsonl) and save the result. I also follow along on the issue tracker; that really helps me understand WTH they're talking about, and the subagents are also directed to post their shipped notes there.

Haha, thanks!

In the context of the union query, I think it makes sense. The query takes two different columns (with two different names) from the same table, and combines them together into one column. The TS error happened because the column names didn't match between the two union inputs. But they would never match without the "as".

Cool! I'm surrealize though, sureglymop wrote a sibling comment! I should have just made a PR, lol.

Totally random, but I had a guess about the ts error. I hadn't seen kysely before, very cool!

  diff --git a/packages/lix-sdk/src/query-utilities/is-in-simulated-branch.ts b/packages/lix-sdk/src/query-utilities/is-in-simulated-branch.ts
  index 7d677477e..39502f245 100644
  --- a/packages/lix-sdk/src/query-utilities/is-in-simulated-branch.ts
  +++ b/packages/lix-sdk/src/query-utilities/is-in-simulated-branch.ts
  @@ -21,10 +21,9 @@ export function isInSimulatedCurrentBranch(
                // change is  not in a conflict
                eb("change.id", "not in", (subquery) =>
                        subquery.selectFrom("conflict").select("conflict.change_id").unionAll(
  -                             // @ts-expect-error - no idea why
                                subquery
                                        .selectFrom("conflict")
  -                                     .select("conflict.conflicting_change_id"),
  +                                     .select("conflict.conflicting_change_id as change_id"),
                        ),
                ),
                // change is in a conflict that has not been resolved

If you fire one board member (Altman) and remove another from the board (Brockman) it's not exactly friendly either

This definition is an abuse of the word "open"

Well, is scraping Twitter an improper use? Anyone can see tweets and who follows who - that's public. Twitter might consider a nascent competitor trying to scrape a significant fraction of the whole thing unfriendly though.

If you're making a twitter clone (as Substack is) then scraping the twitter follower graph seems useful. And that's public, obviously.

I worked at a company that was about 150 people when I joined. It's not primarily a software company but the early team had a bunch of ex-google folks, and they chose Bazel. I encountered it for the first time there. We did use React, yes.

I really liked the cross-language aspect of Bazel. Having one command that could compile everything and produce a deployable container in a highly reproducible way is great. It really cut down on "what's your compiler/tool version etc."-type back-and-forth during debugging with other engineers.

The bazel JS/TS rules were tough to work with when we first started using it for JS (2018 I think), especially since we were using create-react-app at the time, and that didn't mesh well with the way bazel wants to work. It's gotten a lot better though.

If I was making the choice from scratch in a new company/codebase, I think it'd really depend on the team. You kind of need broad-based buy-in to get the full benefits IMO.

> having to stop for hours while waiting for your car to charge is much, much worse

Have you done this? I picture burning some kid-energy during those breaks. I'm genuinely curious about how that ends up impacting the trip experience.

> fluctuating energy costs impact TCO

compared to gas?

There's an original, canonical version of the audio, and the hash of that version goes on chain. That establishes who posted it originally, when, and the exact version. Then any subsequent (potentially doctored) version can be compared with the canonical original. The on-chain timestamp and hash can't be changed after the fact, in the same way that past bitcoin blocks can't be changed (without creating a fork).

It could at least address some kinds of misleading editing. In the political use case, maybe the candidate posts all their event audio and records the hashes on chain. Then they can't change the content of any of it without getting caught. And if someone else posts an edited version, the edit will have a later timestamp, and the candidate can point to their original earlier version and prove that it's the original. That lets everyone else determine which version is the original and which version is the edit.