weird-eye-issue

Yeah I always just thought of MCP as best for the average user and then CLI as one of the tools of choice for power users. Never had to be one or the other, I use both daily

I actually haven't had this happen in several months, they have gotten much better at just ignoring changes they haven't made in my experience. Unless it's directly conflicting with something they are already working on of course then they might change it but at least they will note it

...

It absolutely matters because something like Claude Code has no guarantee that there won't be changes between updates but a model pinned at the API version level that is getting enterprise traffic absolutely does have that guarantee and would be a much more widespread problem...

Unrelated to the models

> this is literally faster to do it yourself

It's literally not unless you already know exactly where it is in the code

Also even if it is I find that the extra mental switching is not worth it, that's why I even have it do basic things like updating the text in buttons these days. There is no point in using my mouse and keyboard to track down a file and then make the change when I can just use my voice to tell it what to change and then wait a few seconds.

Just because you don't know how to do something properly doesn't mean it would be over engineered

Right I'm agreeing with you but if there even is a column that's already in production you should just assume it has data in it so I would favor just a blanket ban on altering columns at all

Altering a column that already has data in production should be an absolute last resort, I don't think I've ever even done it, it's never 100% necessary

But in your example you never even asked it to plan so you could check the implementation before writing it you just asked it to write it directly, so this isn't even a comparison to plan mode

You can still do planning as a phase without using an official plan mode you literally just ask it to plan first...

I mean if you want it to plan something without writing code first you literally just need to ask it to plan out the implementation first it's not exactly a difficult concept

Oh I thought it blocked tool calls like editing files...

You don't need to actually change the tool schema or break the prompt cache to do that. In the tool itself you could just check if it's in plan mode and reject the tool call...

> I guess voice cloning is widely enough available now from other providers that Google are no longer hesitant to ship it.

It's funny because you don't even know what the rest of us are talking about.

Yes, those are not conflicting statements. All rectangles are not squares after all. If you can reply to me and actually put the point that you are attempting to make into words I would be shocked. Give it a try!

You're taking this far too seriously. You'd think I'd committed a terrible crime or something. Give it a break.

Unfortunately I was like this long before LLMs, trust me ;)

And yes I know it's a word, I know at least two meanings it has but in this particular usage I was not familiar with it. Anyways, I was wrong and I will take the L

Thanks I had never seen that word used in this context!

That's true

> Tastelessness and mediocrity and inability to grasp nuance or feign at humility are on full display, not to mention a fantasy for violence

You are doing the same thing, very ironic. At least I'm not the one trying to act like I'm on the moral high ground.

If you think that all instances of using AI to write code is vibe coding and you can't even spell model you might not last much longer

Yes, yes it is.

YC funds companies and we are all aware of that so by saying it's a YC company because they gave them seed money is already exactly the correct wording

Right, that's why it's legal. We all get that

Nobody else is talking about the reusable scripts they create, we are talking about it using inline Python to make edits to files instead of just editing it with the Edit tool. But I don't know why I'm explaining this to you again because you clearly don't understand lol

Vibe coders like you who don't even understand basic fundamentals are pretty infuriating because you don't even understand what everyone else is talking about

My god. They are not reusing the scripts. They are adhoc, inline Python scripts just used to make a single edit. You seem to fundamentally not understand what everyone else is talking about

Sounds like you completely lack all reading comprehension ability

LLMs sometimes like to execute one-off Python scripts to make edits to files rather than just calling the edit tool directly. Both are tool calls so saying that you should have it write code instead of doing tool calls makes no sense because writing code is a tool call for it...

They don't always have a great concept of time so for something like running a full test suite that takes a long time you should just tell it not to do that

> There was always some tension between "make abstraction layer whose adoption depends on users finding it easier to make your own components with than vanilla CSS, which is not unusually hard" and "sell pre-made components"

Do you have an example?

I'm the founder of a SaaS in the marketing industry with tens of thousands of paying users and we have lots of AI powered workflows where small changes between model versions can make some big differences so whenever we update models we have to thoroughly test them which is why we pin them at specific versions which has been a best practice (and common sense) for the last 3+ years