phpnode

What's driving the increase in release cadence here? We seem to get new models every week or so now, is this RSI?

That's the point, those jobs went away, the need for a job didn't. No one seems to know what long term opportunities are going to be created by AI, we only know that it is going to erode existing opportunities.

I would be amazed if the LTV of an instagram account is over $7k. Where are you getting that number?

This kind of narrative is going to bite them just like the "AI will take your job" narrative has. It feels like the frontier labs are taking a massive gamble with public perception here. I assume the goal is to paint the technology as so powerful and dangerous that only a handful of blessed US companies should be trusted to run it, in an attempt to suppress the rise of the Chinese models that are rapidly catching them.

I'm sure they will, but any user extension that interferes with the DOM (as an adblocker does) will break remote attestation, so the website will reject your request.

It is not difficult to imagine that freedom disappearing soon, under the veil of security. It will not be long before Google's remote attestation becomes commonplace, and then it won't be long until the websites you care about start using it and excluding unsigned browsers. The wheels are in motion already and AI is going to speed this all up: https://www.eff.org/deeplinks/2026/07/googles-new-remote-att...

cached thought. running CLIs is impractical and expensive in many environments and a hell of a lot less secure than using MCP

This is interesting because I assume it has suffered the same linguistic degradation as the word "fine" which in some cases means "of the highest quality" but mostly means "meh". I suspect it comes down to the dialect and social rank of the person saying the sentence. Compare how you would perceive:

    "You did a fine job"

or

    "It is quite impossible"

depending on who was saying it.

yup, it's not possible to do it safely with a simple unparameterised type: https://www.typescriptlang.org/play/?#code/C4TwDgpgBAcg9gOwK...

Also, ssalbdivad is your cofounder, just in case you’d forgotten!

so, instead of

    (foo (bar (1 2 3))

you'd prefer

    {
      foo {
        bar {
          1
          2
          3
        }
      }
    }

is that right?

It's very clearly written by AI, which means that the thoughts expressed are not novel and the story told cannot be trusted. How can you expect people to spend time digesting the content if the author did not spend time writing it? It would be more honest to show the prompt, or the unpolished draft.

They overbuilt capacity for grok but no one wants to use grok for several reasons

Goodness me that’s quite a comparison

You are quibbling over minor semantics. Is the US preventing most oil from reaching Cuba or not?

The car reads the speed limit signs too, they don't just rely on GPS.

If your competitor is cutting jobs because of AI you can either race them to the bottom or you can use the humans you already have to leverage AI to expand your product offering, become more competitive, tackle more work, deliver better quality results etc. I don't see a world where AI does the work and humans sit around poor and idle.

They won't. So what? This is not how specs are used, no one is saying that they are a replacement for source code.

People always say this but it’s misguided imo. Yes LLMs are not deterministic, but that’s totally irrelevant. You aren’t executing the LLMs output directly, you’re using the LLM to produce an artefact once that is then executed deterministically. A spec gets turned into code once. Editing the spec can cause the code to be updated but it’s not recreating the whole program each time, so why does determinism matter?

Because if you were building GitHub from scratch today you wouldn't build it the same way and would benefit from many of the technological advancements of the last 2 decades (nearly).

at least one went to Shopify, I'm not sure about the rest

Last time they tried this they laundered it though an employee's personal github to distance it from google itself, then framed the proposal in the most disingenuous manner possible, as if it was something that users wanted rather than another mechanism for google to exercise control

Why do you continue to extend the benefit of the doubt to your former employer when they have shown themselves to be untrustworthy again and again?

Last time this happened we got a bunch of Google employees downplaying the impact of WEI and calling it a nothingburger, that people were being hysterical. I just checked, and everyone I saw defending it has since left the company. I'm sure another wave of Google managers, keen to appeal to the higher-ups, will be here to defend this new initiative any minute now.

it's about the comments / votes ratio.

1. More code faster is not the goal. More features / value faster is the goal. Obviously to get there you need to write more code, but it's not writing code for code's sake.

2. Yes, true, but the point is to move up the abstraction hierarchy, so instead of asking the LLM to rename a variable you describe the concrete business goal you're trying to achieve.

It is true that coding agents cannot build fully complete stable systems completely unguided yet. That's why we still have jobs. But it's wrong to suggest that they don't deliver value or that they're destined to produce trash every time. It is a matter of oversight and guidance and setting your codebase up for success. That does require work, but it is not impossible, just a different skillset from the ones we've been used to.

I have an approach that can handle this if you're interested? My email is in my profile.

If it's genuinely the case that you can write code faster than you can prompt it into existence then you're not being ambitious enough with your coding agent. Ask it to do more. Tackle bigger problems.

it does take a little while to get good at this new skill, yes. Just like, say, learning a new programming language and the ecosystem around it takes some effort. After you get over the hump it's really very straightforward and mostly a matter of knowing the kinds of mistakes the LLM is likely to make ahead of time, and then kindly asking it to do something smarter. If you've successfully mentored junior engineers you already have this skill.

and then people get bored and stop updating them, soon we'll need a graveyard-graveyard to showcase all the failed graveyard projects.