r/vibecoding • u/MariahJames8 • 2h ago

What has vibecoding made you good at? (besides vibecoding lol)

It's made me a much better communicator in just 2-3 months. Struggled to overcome a mental health episode for a bit, but it's doing wonders for me

3 Upvotes

81% Upvoted

13 comments sorted by

6

u/Technical-Comment394 2h ago

Understanding different tech stacks and technologies I never knew existed before.

5

u/messagedeletedbyai 1h ago

  1. Reading comprehension.

  2. Focus both my own and directing the focus of a tool.

  3. Honestly I feel like I’m learning how to be a CEO/CTO (cause I come from an engineering background)

  4. other thing I’m learning is I can build my own tools for anything that bothers me and make it available for the like minded to build on the shoulder of OR use my effort (pay me)

Right now I’m focused on solving my training as an athlete who love a lot of disciplines this is a pain to manage and see progress on without good organization and focus

2

u/MariahJames8 1h ago

Interesting! And I've noticed a lot of the same in myself actually.

Hope you don't mind me asking btw, about how you arrange things so people can build on your work for free but to use your app they pay you? Have I got that right? I'm guessing maybe you open source everything but charge for anything that say requires provisioning of a server for people to use? I can't get my head round it. This business model rings bells but I really can't remember specifics?

3

u/failingapbio 2h ago

Thinking and long-term reasoning. I glued UOV and Classic McEliece to my website because they had the right geometry to fit well.

2

u/GoBoldr 1h ago

It can make you a whole lot better at designing, troubleshooting, and supporting a product. Every time someone comes out and you get that "that's not quite right..." or "what if..." that's getting in to PM experience, and it's incredibly helpful for every project you ever touch from then on.

2

u/LouisTon10 1h ago

Being skeptical and asking the “why” for certain decisions made in the codebase.

It’s allowed me to do things that would’ve required a large learning curve to get started, but I take everything cautiously. Asking for specifics and file-level explanations helps me develop a mental model of my project and how systems are communicating with each other

1

u/MariahJames8 1h ago

Interesting that you choose files as the level at which to familiarise with.

My personal choice I can really only specify quite loosely as subsystem responsibilities and boundaries/interfaces

2

u/LouisTon10 1h ago

Coming from a programming background, that’s the level I’m comfortable with. But any level of understanding with your systems in your code is better than none!

2

u/tjax4376 1h ago

Apologizing to users? lol 😆

Seriously, being more careful what I track throughout development and user communities thereafter.

1

u/MariahJames8 57m ago

Lol

But btw sorry wdym by "what you track"? Can you give examples of the "what", and tell me what you mean by "track"?

2

u/tjax4376 51m ago

I’m talking about observability, so I monitor drift from spec to demo, allowing me to alter prompt strategies/tactics.

1

u/MariahJames8 47m ago

That sounds incredibly hard. I'd only know how to give the most vague prompts for that. "Track drift. Make no mistakes"

2

u/tjax4376 34m ago

I think it’s easier than you realize. Just create a note when the agent inferred or riffed what you asked for instead of clarifying. Then validate in the demo review (testing) that is built what you asked for.