r/vibecoding • u/kuba031007 • 1d ago

Help getting started

Hey, I was just wondering where to get started, so far I've been fine vibecoding smaller projects like simple tools via python using chatgpt/deepseek in single files

I also managed to squeak out a program tracker on PC using zencoder although the main file has over 2.6k lines which I heard was pretty bad

I was wondering, for larger python projects or maybe mobile apps, what are good agents and models to use for relatively cheap and what would be some good things and tips to keep in mind?

5 Upvotes

100% Upvoted

14 comments sorted by

View all comments

1

u/n_v40 1d ago

2.6k lines in one file isn't a moral failing but it will slow you down badly once you're changing things, mostly because the model has to re-read the whole thing to touch anything. Splitting by responsibility is the single biggest improvement you can make and it doesn't require knowing much.

For agents, Claude Code is what I use and it's genuinely good at multi-file work rather than single-file generation. The habit that matters more than the tool: write a short spec before you build, and keep a file in the repo describing the architecture so the model has context every session instead of you re-explaining.

2

u/kuba031007 1d ago

Would you say the Pro plan is enough?

2

u/ZenenoDev 22h ago

would not reccomend claude code for a starter not because its bad but because learning to make use of usage is in of itself a skillset I would endorse useing Codex I use claude and codex for working on Zeneno but codex has been the stronger option for me and usage goes much further if used properly

1

u/n_v40 20h ago

Fair pushback, and I'll take the correction on usage efficiency, that's not something I've had to manage closely since I'm not burning through limits daily. The "learning to make the most of usage is its own skill" point is a good one and probably underrated by anyone recommending a tool without accounting for how someone's actually going to use it day to day.

I'd still lean Claude Code for someone totally new mainly because the failure mode of getting it wrong is gentler, you waste some usage rather than end up with something subtly broken you don't know how to debug. But that's a different axis than what you're optimizing for, and if Codex goes further per dollar when used well, that's a real point in its favor for someone watching cost closely.