| ▲ | blanched 18 hours ago | |||||||
To be clear, I didn't mean this as an anti-AI gotcha. They also said: > We get feature requests, improvements, ideas, feedback So maybe I misunderstood, but it sounded like the design was external (and based on an existing product to begin with). Also, my understanding was that "vibe coding" meant more of "make it do X" as opposed to "here's a design for X, implement it." | ||||||||
| ▲ | thraway3837 18 hours ago | parent [-] | |||||||
Sorry, I was trying to be glib by putting "vibe" in quotes, because I think that term is used for people who have zero experience in software engineering, but when used by senior engineers, it's something else. But, I don't know if some populations would still call it vibe coding. The design is external in that the requirements come from external customers or internal customers (since these applications) are used by both. We're not trying to duplicate or replicate any existing system, but I can't confidently say that I'm not drawing from any prior art. Hope that makes sense. | ||||||||
| ||||||||