I'd argue that the asymmetry has less to do with change vs. no change and more to do with the Republican party currently being an "anti government" party (pivoting to that post New Deal). So less is expected of them in terms of functional governance.

With respect to change: I've heard a lot of commentary that the Republican party today is more of an instigator of change than the Democratic party (being seen as a defender of the status quo), despite the traditional alignment of Republican/conservative/no change. Democrats are seen as pro-institution and Republicans anti-institution.

In case it matters, I personally don't identify with a political party. I just want functional government and politics and I see a lot of dysfunction. I'm an engineer so naturally I gravitate towards systemic solutions to systemic problems.

Presumably democratic reforms could help change the dynamic if they changed the incentives. Right now, it's a politically viable strategy to just obstruct the other party when out of power, and politically unviable strategy for Congress to oppose a president from the same party. Both of which lead to a lot of dysfunction.

As an example, if Congress had multimember districts with an appropriate voting system (e.g. ranked choice voting for all members at the same time), then you can effectively nullify the power of gerrymandered voting districts (the current system, where effectively politicians choose voters rather than the other way around). Doing so would elevate the influence of general elections over party primaries. Then representatives would be less afraid of challenges in those primaries, which is currently one of the major disincentives in opposing the president of the same political party (fear of being "primaried").

Red team might not anticipate this if the spec does detail every expected RPC (which seems unreasonable: this could vary based on implementation). But a unit test would need mocks.

Is green team allowed to suggest mocks to add to the test? (Even if they can't read the tests themselves?) This also seems gamaeable though (e.g. mock the entire implementation). Unless another agent makes a judgement call on the reasonability of the mock (though that starts to feel like code review more generally).

Maybe record/replay tests could work? But there are drawbacks in the added complexity.

> Broadly, I am supportive of arming democracies with the tools needed to defeat autocracies in the age of AI—I simply don’t think there is any other way. But we cannot ignore the potential for abuse of these technologies by democratic governments themselves. Democracies normally have safeguards that prevent their military and intelligence apparatus from being turned inwards against their own population, but because AI tools require so few people to operate, there is potential for them to circumvent these safeguards and the norms that support them. It is also worth noting that some of these safeguards are already gradually eroding in some democracies. Thus, we should arm democracies with AI, but we should do so carefully and within limits: they are the immune system we need to fight autocracies, but like the immune system, there is some risk of them turning on us and becoming a threat themselves.

Basically, he's afraid that not arming the government with AI puts it at a disadvantage vs. other governments he trusts less. Plus, if Anthropic is in the loop that gives them the chance to steer the direction of things a bit (what they were kicked out for doing).

It's not the purest ethical argument, but I also would not say that there is a clearly correct answer.

This isn't even a new problem where a good cultural solution hasn't been figured out yet. Reddit has had bot etiquette for years.

Some thoughts:

- Hardware constraints are real, even at Google.

- Features are often released for enterprise users first, before being released for the general public.

- I only started my current role last year.

- 2 years ago is forever ago in AI and things are changing a lot. For example, with older model generations people used to do a lot more fine-tuning (slow) vs. prompt engineering (fast). The implication is that things that are easier to do today might have been hard to do not that long ago. The rapid changes also create churn for internal platforms and dev tooling.

- Google is less yolo and cares about safety, prompt injection, etc. so some time goes into that

- Typical big company bureaucracy also applies, but TBH there's a lot of pressure to deliver Gemini related stuff so I think there's less of that

Also, I've noticed failure modes in LLM coding agents when there is less clarity and more complexity in abstractions or APIs. It's actually made me consider simplifying APIs so that the LLMs can handle them better.

Though I agree that in specific cases what's helpful for the model and what's helpful for humans won't always overlap. Once I actually added some comments to a markdown file as note to the LLM that most human readers wouldn't see, with some more verbose examples.

I think one of the big problems in general with agents today is that if you run the agent long enough they tend to "go off the rails", so then you need to babysit them and intervene when they go off track.

I guess in modern parlance, maintaining a good codebase can be framed as part of a broader "context engineering" problem.

For more context, I have Anthem Blue Cross health insurance. The cost might depend on your insurance.

Over a decade ago I tried getting the HPV vaccine in my early 20s, but the doctor told me it wasn't recommended for men and that insurance won't cover it. I was young and didn't have the money to pay out of pocket.

I went to Planned Parenthood and got the vaccine last year. At some point they changed the recommendation to men under 45 now and I got all 3 shots free.

Honestly, though I'm glad to have finally got the vaccine it's been a pretty frustrating experience.

The classic advice is basically a caution against being a boring monologuer. And it has its merit. But this is an extra "level 2 conversationalist" lesson. It's the old: "OK remember those rules you learned in level 1? Here's when you can break them".

Th affordance analogy is that you want to give yourself and your conversation partner an abundance of options and opportunities for good conversation. Asking questions often is a way of doing that, but it's not the only way, and not all questions are equally helpful.

I also found this Guardian article from a Google search: https://www.theguardian.com/world/2025/mar/01/shortsighted-t...

I have a feeling you might enjoy that book as it goes into a LOT of detail about government dysfunction with respect to software.

I found the book eye opening and personally it provided me with some new perspective.

For example, a quick Google search shows administrative overhead as around 0.5% of benefits: https://www.cbpp.org/research/social-security/top-ten-facts-...

  Location: California
  Remote: Yes
  Willing to relocate: No
  Technologies: QuickBooks Online, Xero
  Resume/CV: available upon request
  Email: jananyoung (at the popular email service hosted by Google)

Notable experience: bookkeeper for Segment (YC S11) for 2 years (eventually helping them transition to an in-house team as they grew). Also worked with Stellar Development Foundation and Sense HQ.

We’re looking for an additional client. With an expected workload of ~1-2 hours a day, at ~$50 / hour.

We’re NOT looking for: she does not do taxes.

So I ordered canned soup, on Amazon, to be shipped to the office mailroom. Then picked up the soups and kept them in the drawer by my desk.

Here is what Wikipedia[0] says

> Due to the diffing results and the data being compressed with the same coding, SDCH dictionaries aged relatively quickly and compression density became quickly worse than with the usual non-dictionary compression such as GZip. This created extra effort in production to keep the dictionaries fresh and reduced its applicability. Modern dictionary coding such as Shared Brotli has a more effective solution for this that fixes the dictionary aging problem.

This new proposal uses Brotli.

[0]: https://en.m.wikipedia.org/wiki/SDCH