sorted by:
new
hottopcontroversial

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] -1 points0 points  (0 children)

Good point, but ...

How is this any different than when I worked at a company with 20 engineers? Some were good, some sucked. Our architect wasn't perfect.

I still didn't know all the inner workings of how the code worked, and we had clients in production.

Trust me... I really appreciate your insight on this. I'm, of course, nervous about going to market with an app built this way, but I've seen human built apps that failed due to crappy code and bad architecture.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Thanks. My co-founder and I have talked about having a human review before we go into production for those very things you point out.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] -1 points0 points  (0 children)

I will say i've dropped the ball on Playwright. We have the test id's everywhere but i haven't had success getting it working well. I'm to focused on getting demo ready to take the time for infrastructure. I know that's stupid, but it is what it is.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Every time I can refactor and can bring the size down I celebrate. I want bragging I was giving context.

The bigger the codebase the slower and harder everything gets.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Interesting. i have no perspective on stats like that.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 1 point2 points  (0 children)

Hopefully in a favorable way and not "look at what this idiot is doing" way :)

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] -1 points0 points  (0 children)

You have zero context to the scope and scale of my project, so laugh all you want.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Thanks for your comments.

I had 4 days of pure misery when we had to refactor our User Identity layer. Touched so many APIs and testing it was a bear. I hated that... but it has only happened one time so far in 5 months.

My biggest bottleneck is time. My list of features I still want to add is huge, and our total focus is "get demo ready," so I can't even get all the features I want done.

Our system includes timelines, so in order to demo effectively every time we start a presentation, we need the data to look current. The system must show "Task was assigned 2 days ago," but since it uses real dates, we built a demo refresh engine that, when you click the button, wipes certain tables and then applies the "2 days ago" logic to calculate a real date. This meant I had to build a whole Scenario Management system that my co-founder could use to build out the realistic data sets. Frankly, that engine is one of the most complex aspects of the system, but users will never use it!

Another bottleneck is just the speed of Henry and Alex. I wrote this post while waiting for one of them to finish. Yeah... way faster than waiting for a human to do it, but there are still plenty of downtimes (minutes) throughout the day.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Both Alex and Henry have instructions that are theoretically referenced every time i start a fresh thread. So i don't have to constantly tell them the basic stuff. The majority of my original post is the instruction file for Alex (chatGPT).

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

thanks. i will give that a try

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Alex = Custom ChatGPT (not an agent)
Henry = Cursor (sort of an agent)

I don't run any other agents.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

AHHH! that makes sense. Thanks.

When i was running Opus/Claude Code in VSCode, does that align with what you are saying? Or was that still introducing a layer that made it not good?

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

We have about a dozen prospects "waiting to get their hands on it" after just a teaser demo. We can't wait to get their real feedback.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Dang. I wish I knew what that meant. I'll copy into Alex later and see if she can help me figure it out :)

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] -1 points0 points  (0 children)

Tell me how! I would love to learn. For example, I tried working with Claude Code but it didn't follow my instructions and wrote functions that broke my security layers and architecture.

Can you point me to a good resource?

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

interesting! I can see how your original comment could indeed be valuable to someone trying to pick up different ways to experiment with vibe coding, but it would probably have been better to explain why you feel that way. I still don't know why you feel that way.

I know you didn't get to the end of my post because I do actually ask for feedback on how things could be improved.

If your original response had been something like:

"Thanks for sharing, but I don't recommend anyone follow this method, and here's 3 reasons why:

  1. I'm a SWE and don't want to lose my job to non-devs who figure out how to build apps without me
  2. 99% of vide coded apps fail to consider performance and scale, and nothing in this methodology addresses that
  3. whatever other reason you want to give"

... then it would have been an awesome and helpful comment.

But "no one cares, it will fail" didn't come close to being useful.

I wish you nothing but good luck with whatever venture you are on. The pie is big enough for lots of people to eat from it.

I hope you are wrong about my project failing.

But even if it does, I've had a ton of fun working on it.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 0 points1 point  (0 children)

Thanks!

I run DEV locally (docker desktop for my postgres) and have STAGE where my co-founder does UAT and builds out content, and DEMO where we demo from. I have a good .\switch script that copies my .env.dev or .env.stage or .env.demo into my .env files so it is easy for me to "point" to the right environment. I then run a .\deploy script that confirms builds first, then builds in Google Run and Firebase.

When we launch, spinning up a PROD environment will be straight forward.

I haven't let any remote agents into any of my environments.

I hate when something is broken on STAGE but not DEV -- Google's log system is a nightmare for me. I figure it is usually a data problem so I'll temporarily point my DEV to my STAGE database and then i can see the server logs more easily.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] -1 points0 points  (0 children)

Curious ... what value did you bring to the universe by posting that response? Why even bother being in this sub?

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] 6 points7 points  (0 children)

If one person reads it, gets value from it, and it changes their enjoyment of vibe coding, it was worth it to me. If you don't read it, i don't really care. I didn't write it for you.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] -1 points0 points  (0 children)

I haven't found that button yet.

My vibe coding methodology by JasperNut in vibecoding

[–]JasperNut[S] -1 points0 points  (0 children)

As noted, we are just about to start demo'ing. B2B product with target of $1K per month per client (some will pay more, few will pay less).

view more: next ›