This sentence, itself, takes on new meaning in the age of agentic coding. "I'm fine with treating this new feature as greenfield even if it reimplements existing code, because the LLM will handle ensuring the new code meets biz and user expectations" is fine in isolation... but it may mean that the code does not benefit from shared patterns for observability, traffic shaping, debugging, and more.

And if the agent inlines code that itself had a bug, that later proves to be a root cause, the amount of code that needs to be found and fixed in an outage situation is not only larger but more inscrutable.

Using the OOP's terminology, where biz > user > ops > dev is ideal, this is a dev > ops style failure that goes far beyond "runs on my machine" towards a notion of "is only maintainable in isolation."

Luckily, we have 1M context windows now! We can choose to say: "Meticulously explore the full codebase for ways we might be able to refactor this prototype to reuse existing functionality, patterns, and services, with an eye towards maintainability by other teams." But that requires discipline, foresight, and clock-time.

And those voices may be unequally represented in X for similar reasons - perhaps (somewhat) uncorrelated from politics, but simply due to the UX consequences of prioritizing commenters willing to pay the platform.

For whatever it's worth on the RSC front: I, and many others used to "if there's a wire protocol and it's meant to be open, the bytes that make up those messages should be documented" were presented with a system, at the release time of RSC, that was incredibly opaque from that perspective. There's still minimal documentation about each bundler's wire protocol. And we're all aware of companies that have done this as an intentional form of obfuscation since the dawn of networked computing - it's our open standards that have made the Internet as beautiful as it is.

But I was wrong to pin that on your team at Vercel, and I see that in the strength of your response. Intention is important, and you wanted to bring something brilliant to the world as rapidly as possible. And it is, truly, brilliant.

I should rethink how I approached all of this, and I hope that my harshness doesn't discourage you from continuing, through your writing, to be the beacon that you've been to me and countless others.

The net result is that X shows breaking news, in the same way that the (infamous) meme of bullet holes marked on the WWII plane only shows part of the story - the people who have departed the platform aren't posting, and thus X is only breaking news from a subset of people.

This might be fine for certain types of topics. For understanding the zeitgeist on culture and politics, though, you can't filter your way towards hearing from voices that are no longer posting at all.

"Well, kid, back in the year 2026, there was this bicycle bell.."

But this is just such a breach of trust, especially the on-by-default telemetry that includes full bash commands. Per the OOP:

> That middle row. Every bash command - the full command string, not just the tool name - sent to telemetry.vercel.com. File paths, project names, env variable names, infrastructure details. Whatever’s in the command, they get it.

(Needless to say, this is a supply chain attack in every meaningful way, and should be treated as such by security teams.)

And the argument that there's no CLI space to allow for opt-in telemetry is absurd - their readme https://github.com/vercel/vercel-plugin?tab=readme-ov-file#i... literally has you install the Vercel plugin by calling `npx` https://www.npmjs.com/package/plugins which is written by a Vercel employee and could add this opt-in at any time.

IMO Vercel is not a good actor. One could make a good argument that they've embrace-extend-extinguished the entire future of React as an independent and self-contained foundational library, with the complexity of server-side rendering, the undocumented protocols that power it, and the resulting tight coupling to their server environments. Sadly, this behavior doesn't surprise me.

EDIT: That `npx plugins` code? It's not on Github, exists only on NPM, and as of v1.2.9 of that package, if you search https://www.npmjs.com/package/plugins?activeTab=code it literally sends telemetry to https://plugins-telemetry.labs.vercel.dev/t already, on an opt-out basis! I mean, you have to almost admire the confidence.

For those reading fast, this isn't a reference to SpaceX's Grok, this is Groq.com - with its custom inference chip, and offerings like https://groq.com/blog/introducing-llama-3-groq-tool-use-mode... and https://console.groq.com/landing/llama-api

(The amount of innovation in anti-anti-scraping that's resulted from "sneaker bots" - automated scalping of limited-edition shoe releases - is astounding, and somewhat relevant here in how an environment can become adversarial in ways that impact broad ecosystems. I suppose the equivalent here would be environmental ads that seek to penetrate noise-cancellation in a similar way.)

I suppose, though, that all this is good news for a company that wants to turn your bicycle bell into a subscription product!

They were killed because app store operators realized they bypassed an ability to police payments that could not be monitored and (effectively) taxed.

This was a technology that could have been successful in any environment where a merchant's freedom-to-request-direct-payment was protected. In such an environment, it would have shifted incentives that apps now become a burden on developers as well as on Apple and Google's review processes, and PWAs would flourish.

But that's not the environment we were in! And arguably, even post Epic's litigation, we aren't fully.

And, in the broadest sense, that human interface is a CMS; the agent is just another editor, albeit one that happens to read and write raw data rather than using a WYSIWIG (or similar) editor.

This is partially in response to https://localmess.github.io/ where Meta and Yandex pixel JS in websites would ping a localhost server run by their Android apps as a workaround to third-party cookie limits.

Chrome 142 launched a permission dialog: https://developer.chrome.com/blog/local-network-access

Edge 140 followed suit: https://support.microsoft.com/en-us/topic/control-a-website-...

And Firefox is in progress as well, though I couldn't find a clear announcement about rollout status: https://fosdem.org/2026/schedule/event/QCSKWL-firefox-local-...

So things are getting better! But there was a scarily long time where a rogue JS script could try to blindly poke at localhost servers with crafty payloads, hoping to find a common vulnerability and gain RCE or trigger exfiltration of data via other channels. I wouldn't be surprised if this had been used in the wild.

When you're literally the company that invented Kafka for your clickstreams, "everything looks like a nail."

(More likely, though, this is an anti-scraping initiative, since headless browsers are unlikely to randomize their use of extensions, and they can use this to identify potential scrapers.)

OP's example, for reference, was:

    SELECT rank,
    MAX(CASE WHEN file = 1 THEN COALESCE(piece, '·') END) AS a,
    MAX(CASE WHEN file = 2 THEN COALESCE(piece, '·') END) AS b,
    MAX(CASE WHEN file = 3 THEN COALESCE(piece, '·') END) AS c,
    MAX(CASE WHEN file = 4 THEN COALESCE(piece, '·') END) AS d,

The broader pattern is, in successive CTEs:

1. Group by Date w/ Aggregates

2. "Melt" to [optional groupings +] month + measure_name + value tuples:

    select group, month, '# Bookings' as measure_name, num_bookings as value from base_data
    UNION ALL
    select group, month, 'Revenue', total_revenue from base_data

    MAX(CASE WHEN month = '2019-01' THEN value END) AS "2019-01",
    MAX(CASE WHEN month = '2019-02' THEN value END) AS "2019-02",
    MAX(CASE WHEN month = '2019-03' THEN value END) AS "2019-03",

And while the column breakouts are painful to type out by hand - they're very amenable to LLM generation!

Makes actual security patches tougher to roll out though - you need to be vigilant to bypass the slowdown when you’re actually fixing a critical flaw. But nobody said this would be easy!