> All designers should be able to code and do html/css. It's the medium of design.

So a fashion designer can mass produce clothing? So an interior designer can build a house?

This designer should has never held.

Fashion designers can, in general, work with fabric, yes. And an interior designer should probably have some idea of how to paint at the very least. To me with web design so much of what matters is encoded in the CSS and HTML that it is the final design product. Anything produced before is a sketch, a concept, but it's not a design.

The analogies you have offered aren't great.

For example designers and developers both use the computer as their primary medium of working. Their outputs resemble each other very closely, despite having a different underlying form.

Contrast that to the interior designer building a house, well those are different mediums. There is no efficiency gain from the interior designer designing the plan and also implementing it. Where as with a designer working in code there is one.

Fashion designers do indeed make clothing by hand, it's a very important part of their craft. This example disproves your stance.

> outside of winning benchmarking charts

Prisma didn’t win the benchmark charts either.

Yes, and?

That was the point, delivering business value within a specific set of KPIs makes more sense than winning benchmarks, if the outcome remains the same.

> That was the point

Of what? Doing Rust? Prisma Rust failed to win the benchmarks.

Prisma Typescript also fails to win the benchmarks.

> if the outcome remains the same

Then don't drive a car. You can walk. The outcome is the same.

> sweep with Mythos to remove any existing bugs and protect it from any cybersecurity attacks

Maybe Mythos went in too hard and removed the physical network too?

> The product has always felt obvious to us: teams waste 45+ minutes per incident just context-switching between Grafana, AWS Console, PagerDuty, and Slack before they even start debugging. We collapsed that.

This sounds more like a symptom than the actual problem. They shouldn't have to context switch. Using LLMs to stitch it together is like adding glue to broken glass.

> And every week another enterprise tells us their infra team wants to "just build it themselves with Claude."

This might not last. Reports already keep coming up on issues with Claude for example. Also any "rewrite" from scratch looks good on first go. Time will tell.

> To improve this, we have shipped a few UX improvements (eg. to nudge you to /clear before continuing a long stale session)

Is this really an improvement? Shouldn't this be something you investigate before introducing 1M context?

What is a long stale session?

If that's not how Claude Code is intended to be used it might as well auto quit after a period of time. If not then if it's an acceptable use case users shouldn't change their behavior.

> People pulling in a large number of skills, or running many agents or background automations, which sometimes happens when using a large number of plugins.

If this was an issue there should have been a cap on it before the future was released and only increased once you were sure it is fine? What is "a large number"? Then how do we know what to do?

It feels like "AI" has improved speed but is in fact just cutting corners.

> When I hear: I'm not good at frontend, I'm good at backend - I'm starting to think this is not true.

There's no absolute true false in anything like that. Generalization is just an easy way to reduce thinking.

To take that analogy further - when you go to a specialist (doctor) and get assigned 1 are they the best 1? If you have a different problem do you have to go to a different specialist?

So it's not about you. It's about society or your company. You get a job, e.g. backend engineer. That's your "label". It doesn't actually say what you're better at -- just that you were tested for backend by company standards and got in.

> It doesn't really make sense since you're not going to achieve an advanced node from a standing start in a practical time frame and cost.

They already announced a partnership with Intel.

Oh the irony.

He may just want to buy them, to accelerate things, once SpaceX IPOs

But they have personal superintelligence?

It doesn’t do the same thing. Each has its own system prompts, tooling etc.

GitHub copilot sometimes doesn’t give you the model’s full context or something else.

The issue is also what does the model mean? Is Opus on Copilot the same as in Claude direct? There’s been lots of hosting providers trying to save money and cut corners. Some employ compression techniques.