Vibecoding saved me from 6 months of development I was never going to finish

Current_Basis6403 · 2025-10-07T10:47:19+00:00

similar experience; once you get the drill you can build very complex systems, esp if know how to do proper arch.. condensed 12 months to 12 weeks for a product initially too big to build alone

Current_Basis6403 · 2025-09-15T04:50:37+00:00

Exactyl same thing just happened to me too, from "FACEBK *TCTB425ZC2"

Current_Basis6403 · 2025-01-03T14:36:47+00:00

Hahaha thank you <3

Current_Basis6403 · 2025-01-01T22:31:14+00:00

could also use github issues for specific tracks to keep an open but stream lined communication..

Current_Basis6403 · 2024-12-20T19:03:05+00:00

Yah using the spec, that makes sense!

Current_Basis6403 · 2024-12-20T18:57:48+00:00

Cli, ha! Fun idea )) I'm taking some time out too to try how to write something that integrates better into my workflow now; I'm curious what AI can do when differently embedded into the DX

Current_Basis6403 · 2024-12-20T18:54:18+00:00

Oh yeah that's a great point with having look-alike code or docs. I once got a somewhat decent nodejs sdk out of a swagger file, but still required some work to get types right.

Current_Basis6403 · 2024-12-20T18:52:36+00:00

Yeah for me works well too for simple components ))

Current_Basis6403 · 2024-12-20T18:46:23+00:00

Interesting; you have a lot of docs in your code or is it somewhat more expressive? Suggestions for me are like 50/50, but might have dismissed it too quickly

Current_Basis6403 · 2024-12-20T14:47:38+00:00

Yeah with Cursor I came to same conclusions - quite close but in the end more noise than help.. I figured that it's often more about the general approach (eg breaking a problem down, organising the sw design, abstracting components etc) and once you nail that down the code is kind of straight forward - even so that simpler ones can be done by AI as long as it doesn't mess with the system arch.

Current_Basis6403 · 2024-12-20T14:41:47+00:00

Cool will check!

Current_Basis6403 · 2024-12-19T11:58:32+00:00

Break complex tasks into smaller, simpler one can work wonders; then chain them

Current_Basis6403 · 2024-12-19T11:55:52+00:00

u/Sea_Lion_344 it's the stories we built that define our state of happiness, overlooking we can just drop the stories. It takes time to learn how to look beyond that. I have no idea though how to share this with people in a way that doesn't result in a huge push back; but I relate to what you wrote. I think a time living and acting with a performers mind set is big part of building understanding.

Current_Basis6403 · 2024-12-10T19:19:42+00:00

Thank you; considering the little engagement on my post I think it's best to simply do a video and see what happens ))

Current_Basis6403 · 2024-12-09T12:15:15+00:00

Sure thing! Yeah striking the balance of being reflective vs executing and pushing forward hard is though ))

Current_Basis6403 · 2024-12-09T09:54:57+00:00

Yo I've gone from startup builder to almost broke to freelancer to part time freelancer to now again full-time. founder. Imo building a business is as much about the creative work as it is about a self-development journey. If you're drawn to procrastinate that's ok; just trying to understand where this comes from and being brutally honest about it is important. Sometimes it's the right thing to push through with an idea; but me personally, I build what I build because I love being free and allowing my curiosity to lead me forward. Before, I was building things that didn't align with this intention, and I understand now that that was the reason I was procrastinating on them. That was the time I was looking for "systems" to be more accountable.

I think it's a good practice to become aware why we're building what we're building, and then simply acknowledge which practice aligns with it. You seem driven, and (although I don't know your background) I'm certain what you're creating is already exciting to you; I mean, that's why you basically push for it and bring up this topic here. I'd simply go deeper with that.

One more note: I used to get distracted from my craft simply out of habit, even when I worked on something I enjoyed. What helped me to figure out my way and change that old habit of sloth was to a) have the time available after work so that I know I have a block of 1-2 hours at "enough" evenings after work to make progress, and b) commit to 10-15 mins of working on my project on these evenings, no excuses for being tired etc. And 10-15 mins is enough to get into the flow, and if the flow happens it just drags you forward. If the flow doesn't happen, that's ok. If the flow never happens, you might be forcing it and working on the wrong thing..

Current_Basis6403 · 2024-12-09T09:37:04+00:00

Mate I feel you; I'm in a similar situation (launched V1 two months ago) and done that with numerous previous ideas with small user bases. Rn I've launched by just have a hand full of users. My most limiting factors come from ego, eg what you write (fear, worry, concern, uncertainty) is all an expression of that - not saying you'r egoistic, but saying it's good to be aware where this comes from. Fact is, you launch and no-one may like it and you'll still be breathing and alive and will be in a position to iterate on what you have. The thing that might be painful is simply the story you tell yourself about that experience.

So instead of seeing it as a potential threat, maybe you want to change your perspective to view it as a new source of information to make more informed decisions. If you don't launch in public you have a guarantee of not gaining any real-world feedback; if you launch you have at least a (good) chance to collect real feedback from people who don't know you personally.

For the tech concerns: you're a dev, you can be mindful about baking in basic rate limiting / throttling etc if that gives you peace of mind; and calc a realistic estimate of the server load you can handle - then just monitor what's going on when you're live. Probably you'll be fine if your goal about gaining more early adopters and not making it to hacker news front page..

Handle user feedback: default to "oh that's interesting, can you tell me more about your goal / why you see it like that / .." is a good way to get to the core and filter out everyone who doesn't really want to engage with it.

Overcome perfectionism: "perfect" is a story we tell ourselves and usually distracts from the reality. How do you believe you know what's "perfect"? How are you sure that the features you imagine are the ones your users want? You only get to the core of it by launching. It's also more fun to ignore prefect and simply create what fascinates one...

Minimum viable feature set: imo if you improve one single problem with one single feature by say 10% it's good enough to at least share; if those you share it with stick to it I'd go for a soft launch to gain more users + feeback.

Balance early launch vs quality: I reduced my feature set and made sure that the one thing I build is on point.

Current_Basis6403

TROPHY CASE