Live data from Hacker News

Vibe Coding: Developer Slot Machines (Cursor, Windsurf)

prototypr.io

31–37 of 37 posts

Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)

#31
post #30
post #15

This article is really difficult to read or its just me? The breaks with the adds are really distracting and I don't know what the author actually is saying here, that he will try windsurf? Do I need to watch the video?

I had the same thought, basically here's a summary, as far as I can tell: > AIs are sometimes good for code, sometimes not so good. I put some money in but don't know what code will come out, and it's so easy to put more money in. My friend told me to use Windsurf instead of Cursor, and it's easy to switch IDEs, they have no moat. Where's the moat? AFAICT, that's the whole article.

[deleted]

Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)

#33
post #28

Speaking about agentic coding I have a question about Copilot in VSCode. In agent mode (need to enable it manually in settings), did anyone test forcing Copilot to run unit tests after code changes and fix code to pass tests if they break?

That's what I do as standard in Windsurf. I set memories for it to run the tests too. That's standard, right?

Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)

#35
post #33
post #28

Speaking about agentic coding I have a question about Copilot in VSCode. In agent mode (need to enable it manually in settings), did anyone test forcing Copilot to run unit tests after code changes and fix code to pass tests if they break?

That's what I do as standard in Windsurf. I set memories for it to run the tests too. That's standard, right?

I just tested and yes, it works.

My issue was my instructions.md file telling it to think too much before writting files and running tests. So it was in a rabbit hole of ethernal thinking.

Now I can tell it to create crud pages and it will generate and run tests for those pages as well.

Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)

#36
post #33
post #28

Speaking about agentic coding I have a question about Copilot in VSCode. In agent mode (need to enable it manually in settings), did anyone test forcing Copilot to run unit tests after code changes and fix code to pass tests if they break?

That's what I do as standard in Windsurf. I set memories for it to run the tests too. That's standard, right?

How do you solve the risk of AI writting and executing unit tests with something like `rm -rf /` and wiping your files?

I'm looking for solutions. Docker looks like one but I like to keep things simple.

Re: Vibe Coding: Developer Slot Machines (Cursor, Windsurf)

#37
post #36
post #33

Earlier quoted context omitted.

That's what I do as standard in Windsurf. I set memories for it to run the tests too. That's standard, right?

How do you solve the risk of AI writting and executing unit tests with something like `rm -rf /` and wiping your files? I'm looking for solutions. Docker looks like one but I like to keep things simple.

You can set only allowed filepaths for file handling. I don't there's an explicit way to guardrail it to not run something bad from a shell though (althogh you need --no-preserve-root nowadays in that rm command). You'd have to check every command before running. It's anecdata but I've been doing this stuff for a good few months now and it's not tried to delete my filesystem or lock me out of an airlock, just yet.
Post reply on HN