I imagine the worst mistake you can make as a programming beginner is to start your journey with vibe coding
Login to reply
Replies (26)
For those (i.e. me) who want to do a deep dive on ecash, what is the best starting point? Non-dev..
Well, at least it’s a start, may open the doors to some folks but 99.9999% of them will not get hooked anyway 😂
Doubt it. The worst mistake would be to not start at all.
I think it's a great learning tool, just like games are. Whatever keeps you engaged and curious. Vibe coding potentially does both.
A good teacher does both too, a bad one neither.
Pro tips: if you are new don't copy-pasta, actually understand the thing and put in the work.
View quoted note →
you're not giving enough
I tried learning a few years back, I kept getting stuck on errors just setting up my environment. Yeah… it was frustrating just to get started and I gave up.
Fast forward to today I love vibe coding. I may not be learning from scratch but I’ve leaned a heck of a lot more already just trying to debug my apps. Keep in mind I’m not trying to become a developer, that was never my goal - I just wanted to create stuff and now I’m doing that. I can actually use the stuff I make. I couldn’t care less who else uses it.
I think I’m where you were a few years back. I should probably give it another go just to build stuff for myself.
Bingo. Vibe coding is scratch your own itch on steroids. And nostr allows you to actually scratch it, and scratch it deeply.
Bad take, grandpa 👴
dont listen to the haters, i think AI will augment anyone's current skill level in anything, making everyone who bothers to learn it (which also takes time and effort) a force multiplier. its exciting and we are only scratching the surface so far..
carry on 😁
Agree with what you said but even vibe coding can't learn the principles for you: types, data structures, basic algorithms.
There is a wall that you can't break through with vibe coding. I've been vibe coding myself for more than 3 years at this point.
I've been vibe coding before it was cool
Agree with that but I can hardly call that programming, maybe one-shot problem solving or something like that.
Yup I think I'm talking about being a developer, not the practice of programming
read the nuts and check out the nutshell code. It's easy to read (at least I hope).
Most of you say "I've learned so much vibe coding" and that's great. What you mean though is like learning physics by watching YouTube videos. What I mean is learning physics by going through hell, solving problems night over night and losing sleep and hope, thinking that you will fail, and then having the aha moment that nothing else can give you than sustained hard core pain.
Nothing can do the learning for you and your brain's capacity is limited. Experiencing that limit and being comfortable with it is what makes you a great coder / mathematician / physicist imo.
There is no free lunch
it's a good mean to learn something, but you'll get a much superficial knowledge compared to actually studying it
docs.cashu.space
I've been wondering about this so much. I'm learning Python and wondering if there's a point 😅
The deeper I get into Python the more I realize how important it is to understand code from the bottom to top.
So for now: vine coding is great fun for quickly getting ideas "on paper". As soon as that stage is over I think it's really important to know what you are doing and to have experts.
I think one day soon that’s going to be like saying the worst way you can start your journey is using a high level language instead of assembly or straight binary
TDD
Unfortunately, we're wired to follow the path of least resistance, and that's what prevents most people from reaching their full potential—especially today.
The knowledge gap between junior and senior devs is about to boom.
Corporates will start hiring only 1 snr dev per team.
But what happens in a few years when those snr devs retire?