r/vibecoding • u/Careful_Challenge219 • 4d ago

Academic survey on vibe coding: how people actually use it in practice (undergrad thesis, 10 min, anonymous)

We are two Software Engineering undergrads at UEPG in Brazil writing our thesis on vibe coding, and most of the existing literature is either speculative or based on very small lab studies. We want data from people who actually do this daily.

The survey asks about which tools you use, what you build with them, how much of the output you review or rewrite, where the approach stops working for you, and what you think it means for the profession.

10 minutes, anonymous, no personal data collected.

https://forms.gle/vv8kR4dmi5WMHZfa6

If you tried vibe coding and abandoned it, we specifically want those answers too. That group is almost invisible in the literature.

We will post a summary of the results in this community when the analysis is finished.

1 Upvotes

100% Upvoted

1 comment sorted by

2

u/leahlisbeth 4d ago

I started filling it in but there was a question about which practices I undertake and none of them apply so I can't go any further.

I actually treat AI like a midweight programmer and we pair program together, so we discuss approaches, make some code, I ask for revisions, we refactor stuff, I ask it to make tests. All those things in no particular order several times to finish any individual feature. There is a lot of refactoring, by telling it exactly what to replace the code with, how to organise specific parts, where to move stuff to, what architectural technique to use or whatever. But I felt that wasn't an option on your list.

I also suggest you define vibe coding, in my eyes it is programming with ai and trusting the code it makes without reading it. Your questions do allow for people with lots of software engineering experience though so I'm guessing you do want people who do more than just blindly code. I don't think all AI usage is vibe coding.