|
|
|
|
|
by motorest
338 days ago
|
|
> If you had no prior experience building that exact thing, writing that spec would be 95% of the work. Nowadays most mainstream LLMs support pre-bundled prompts. GitHub Copilot even made it a major feature and tools like Visual Studio Code have integrated support for prompt files. https://docs.github.com/en/github-models/use-github-models/s... Also, LLMs can generate prompt files too. I recommend you set aside 10 minutes of your time to vibe-code a prompt file for PCB generation, and then try to recreate the same project as OP. You'd be surprised. > Anyway, I don't think the experiment is wrong, but it's also not exactly vibe-PCBing! I don't agree. Vibecoding doesn't exactly mean naive approaches to implementations. It just means you enter higher level inputs to generate whatever you're creating. |
|
Sure, but the utility of that for PCB design wasn't demonstrated in the article. This is an expert going out of his way to give the LLM a task it can't fumble (and still does, a bit).