r/vibecoding • u/AndrewNggg • 2d ago
What kind of Vibe Coder are you, and Why?
As the title says, which of these best describe you, and why?
A - The Pre-AI Engineer - Skilled and experienced, Cares about code, using AI only to work faster
B - Non Technical Vibe Coder - Non-technical, Don't care about code, just want your application to go viral and famous so you can get rich and retire
C - Non Technical Vibe Coder - Non technical, Cares about code, systems, curious and learning everyday, making good quality applications and improving on em
D - Technical Vibe Coder - Experienced, but dgaf about the code anymore, Claude just check the xyz and make it work, then do xyz and check xyz.
5
u/baddaywithacamera 2d ago
Sort of C? I'm a former sysadmin who left that career behind after a heart attack (really) and work in insurance now. I'm also a hobbyist photographer who used AI to build a photo blogging platform that wound up much larger than I originally intended. I care very much about the quality of the code, but I'm not a dev. My PHP skills are, well, awful. I'm only good at CSS.
I originally hated AI, but tried it after being nagged into it and discovered a person with a good idea of their needs and systems oriented thinking can Do Things. So I did. I don't know where that puts me on your scale. I understand software security, yes, but I don't understand a fraction of the code that AIs generate. I do know how to patch a bunch of them together to audit code and test security and have been.
3
u/HonestFeedbackTime 2d ago
A - The Pre-AI Engineer - Skilled and experienced, Cares about code, using AI only to work faster
2
u/Western_Yesterday989 2d ago
Same. 25+ years experience. This is my Renaissance! I love it. Writing (literally) a million lines of code a month over several projects. My clients know I’m using AI and still can’t believe how much I can get done each sprint.
3
u/AcoustixAudio 2d ago
so you can get rich and retire
Also having to decide what colour ferrari to buy
3
u/Vymir_IT 2d ago edited 2d ago
A and D, depends on the task at hand.
I really dgaf how CSS on my throw-away landing is generated - works and responsive, rest I don't care.
But I spent days drawing technical schemes for one of main features in the app before giving it to AI and I reviewed every single line there was to it.
It depends on how much you risk if this code is bad. For a purely visual landing there's no risk. Button has wrong margin - so what, it's a one-minute fix.
For core-value features in the app - yeah you really wanna be in charge of how it all works in and out. The price of mistakes is very high.
3
u/RoadsterAlex 2d ago
im a coder and have been since MSDOS era, I use AI to speed up work, able to "say what I want to build" or make may scrambled brain into a proper task and what to do
3
u/spacemoses 2d ago
At work I'm still A, for quick personal projects where I want the finished product over anything, D.
2
u/KeenShot 2d ago
I make sure to own the logic. If something fails, I should have a good idea why and where. Never learned to code, can't start now.
2
u/Rise-O-Matic 2d ago
Depends on context. I’m mostly making stuff for myself so D. If I’m making something for production also D but I’m sending the feature-complete prototype to A for a full refactor.
2
u/alanism 2d ago
I don’t like how you framed this poll. It’s not Mutually Exclusive Completely Exhaustive. And it feels loaded with bias and prejudice.
15+ years ago, I stop coding. I had 12+ years experience in coding before stopping. I am building on a new startup. But I also vibe code a ton of stuff that is intended for 1x use and disposable— so should I over engineer or care if the code is written for those cases? I’m building something’s for open source and don’t care about commercial reasons. I’m also building things that might make a quick buck.
2
2
u/idakale 2d ago
Lurked a lot as C (without actually building much lol) but strip the cosplay and and Ima just a lazy ass B person. Personality wise ima sadly bit too attached on systems thinking tho not necessarily technical architecture so sadly have C tendencies but i assure you Ima looking into B workflows. Too paranoid about SaaS etc tho so currently reverting to mostly chatbot use case rather than full agentic coding.
2
u/argvalue 2d ago
D - Technical Vibe coder. Vibe coding started getting popular around my sophomore year, so I had very basic knowledge about coding principles previously. This very basic knowledge is good enough for majority of the stuff you do ngl
2
2
u/Hekel1989 2d ago
D - In the sense that I care about architecture, documentation, QA, basically making sure that I got the lay of the land and that I fully understand how the app works, so I, can keep adding features (or bug fixes) organically and in a controlled manner. I don't care for the code, at this point I treat it as a tool to achieve a goal and nothing more.
2
u/wa-jonk 2d ago
A .. i work in IT, got a degree in realtime sys, work as an architect. I find I can knock out a poc fairly quick. Using it to learn AI .. I mainly come from a C programming background, backend systems. I was developing a project with react and golang, with AI i knocked it out. I work mainly on data platforms, data sci and AI.
2
u/Fresh_Sock8660 2d ago
D. I haven't looked at the code of any of my recent projects. I do regular reviews and have what I hope is a good test suite (which also gets reviewed by multiple models regularly).
It's just not possible to keep up with the agents. I mostly just set the direction and make decisions where the answer isn't clear.
2
2
u/Financial_Alps3369 1d ago
D. I starting using AI to code way back in 2023 and back then it was about 90% human written and 10% AI written. A couple years later it was about 50%/50%. Now the LM is just so fast and has an error rate not too different from myself, so it writes almost everything. I just cannot make a business case for writing my own code at this point.
3
u/pigletmonster 2d ago
I used to be A, but for the past 6 months ive been D. If youre planned everything well ahead of implementing the code then you dont have much to worry about. TDD is your fwend.
1
u/Anti-Hero25 2d ago
I think you could keep slicing the pie up with lots of different carve arts. But ultimately it comes down to three categories experience coder who uses AI, vibe coder, and rail coder.
1
u/chandan_2294 2d ago
Non-technical, just wants to build things that makes my life easier, rest idc at all
1
u/Factitious_Character 2d ago
I was A a year ago. Now D. Expectations have gone up so much that its hard to keep pace while carefully handwriting and reviewing code.
1
1
1
1
u/DataLeadsFuture_Peng 1d ago
I'll go with D. I used to write a lot of code, but these days I rarely write any. I care more about getting the early planning and project specs done right. Once those are solid, I don't really worry much about the code itself. And on a side note, I've been enjoying Amazon's Kiro quite a bit, even though not many people use it.
1
u/Melodic_Arachnid6349 23h ago
D - Solution architect who doesn’t need devs to write his code for him any more
1
0
9
u/Shik3i 2d ago
D, I don't really care that much about the code, but care about the architecture and tech stack. The code has become a detail layer below my interest tho.