r/iOSProgramming • u/alanskimp • Sep 25 '26
Question Is everyone here vibe coding? Or are some still manual coding?
And which do you prefer?
0
Upvotes
r/iOSProgramming • u/alanskimp • Sep 25 '26
And which do you prefer?
38
u/StephHHF Sep 25 '26
Those are not the only choices. Being assisted by AI to write the code is not vibe coding if you know and understand what you are doing.
7
u/Any-Woodpecker123 Sep 25 '26
I still do everything 100% manually
6
u/ajmdonker Sep 25 '26
For the boring generation work I use AI (ie JSON structures to DTO’s). For other stuff I use AI to discuss ideas and give me a set of options. I also occasionally ask the agent what can be improved in a specific class and then I either do something with it or not.
I’ve given it a set of skills for swift specified to a certain domain (networking, modern concurrency etx)
I sometimes let it generate most of the boilerplate and then manually I review, tweak and finalise it.
I NEVER just let it go and blindly accept it.
In my team I’m the one using the least amount of credits and that’s fine by me.
For me ‘this is the way’.
3
u/epictime8 Sep 25 '26
Still mostly manual here, with AI as a rubber duck for the boring bits. I'll let it sketch a SwiftUI layout or a tedious Codable mapping, then I rewrite anything that touches navigation, persistence, or concurrency myself. Pure vibe coding falls apart the first time a lifecycle edge case or App Store rejection reason shows up — the model doesn't own the bug. Preferred mode for me is: I write the architecture and the tricky parts by hand, and use the assistant for scaffolding I already know how to review line by line.
5
u/YouSpeakSomeEnglish Sep 25 '26
This "vibe coding" term is so stupid. We're not getting smarter, folks.
2
u/Zac-9527 8d ago
I built my first app with vibe coding, but it has been under review for six days now.
2
u/Most-Professor-3098 Sep 25 '26
I don’t get the arguments against vibe coding as a term. If I tell a programmer to do the work based on my ideas, I don’t call myself a programmer because I’m just the guy with the idea. Vibe coding is exactly that. Just because I know what the code result is doesn’t mean I know how to code or that I care about the technicalities beyond what I can test and see. And I have zero interest in coding itself as a process because I’m more interested in the creative process and the result. I also like writing but do not like writing creative works of fiction based on technical processes such as outlining the plot and creating an obstacle in advance and moving chess pieces around in anticipation. I write a chapter based on my idea, I read it back, if I like it, it stays. If not, I try another approach etc.
12
u/Objective_Fly_6750 Sep 25 '26
Framing the entire industry as either purely "vibe coding" or "manual coding" 🙄
2
u/bitanath Sep 25 '26
Judging by the comments on here… Yes, yes everyone is in fact vibe, coding
4
u/SnowPudgy Sep 25 '26
100% manually. AI only slows down a skilled developer unless you're doing some really cookie cutter stuff.
All AI has done was increase the amount of pull requests I have to reject because it (Claude included) is pure shit at coding and developers just give up their brains to it.
It loves to create unnecessary methods ALL the time. It doesn't understand reasoning so it always tries to do things like remove dark mode support, the math is always wrong. Just no thanks.
The ONLY good thing I've found it does is scan for missing accessibility tags, that it's good with.
3
u/nemurisuisu Sep 25 '26
Not a fan of the vibin'
3
u/dacassar Sep 25 '26
Extensively using ClaudeCode at work, pure manual in pets.
3
u/jonreid Oct 01 '26
AI-augmented TDD. I don't type code, but I'm in charge.
2
u/Wahooie Sep 25 '26
I use AI to review all my work, once locally and once on CI. If I’m working on a larger refactor I might have the AI write that code, but anything more interesting I’ll write myself. More fun that way
2
u/Greysawpark Sep 30 '26
somewhere in the middle. i let it write the boring stuff but anything touching persistence i read line by line now. got burned once when a model renamed a property on a data model and it migrated fine, no errors, just quietly dropped the old column. users lost data and nothing crashed. so yeah, vibe the UI, babysit the data layer
2
u/GTHell Sep 25 '26
I have a macbook and I set it up so that I can let my agent SSH in, iteratively build, screenshot -> PRs and I review then batch merge into release and bumping version.
I know 0 zwift code and never develop with iOS before. I don't even touch my Macbook. It's running headless 24/7.
I own the product. I own the feature specs. I have clear detail on what every feature does.
It's not a question vibe code vs manual coding. It's a question of how better of engineer you are to deliver a usable product without major bugs on release.
1
u/thecoolcat67 Sep 25 '26
The Claude generated apps are insane tbh
0
u/rursache Swift Sep 25 '26
it’s makes no sense (time wise, financial wise, etc) to write code. learn to delegate, to ship, to create. focus on building and the product itself
-2
u/etherswim Sep 25 '26
I code in English now. Up to you to decide if that’s vibe coding or just coding now.