Learning full-stack development, how do I make it fun?

Hello everyone.

So I've been vibe-coding for the past few years now, mainly for fun and curiosity, creating tools for crypto trading, analytics, playing with LLM APIs and other stuff like that. From all of the side-activities I've had in my life, vibe-coding has sparked my curiosity the most. Although, as much as I loved it, there was always a looming issue in the background - I have no clue what code the model writes, I just know it works when I hit enter.

As time goes on, I find myself wanting to create more and more complex logic, and recently, I was captivated by the idea of building my own SaaS, but here is where vibe-coding simply won't cut it anymore. So I decided to sit down, and actually learn how to code. I have one major fear though - it's that I've tried learning before, many times, and I would always find myself quitting. And even though this time truly feels different (I think I have a much stronger "why" now, than I did before) I want to be absolutely sure of it. I think that one of the best ways to motivate myself, considering the complexities of coding, is to make it fun, so this is exactly my question to all of you self-taught, or traditionally-taught coders out there:

What advice do you have to make coding a fun learning experience? I understand that there will be times where I'll bang my head against a wall, no matter how "fun" the outcome of what I'm coding seems to be but there might be some nuggets of wisdom some of you might share, so that the banging doesn't happen that often.

Thank you.

bro i feel this so much full stack can get boring quick if u treat it like a textbook. best hack? build smth dumb but useful for urself, like an auto tracker or meme dashboard lol. btw what stack u leaning toward first, react + node or smth else?

paymentprocessor said:

bro i feel this so much full stack can get boring quick if u treat it like a textbook. best hack? build smth dumb but useful for urself, like an auto tracker or meme dashboard lol. btw what stack u leaning toward first, react + node or smth else?

Click to expand...

Solid advice, thank you, and yeah, the "textbook" feeling is something that I absolutely want to avoid at all costs (although sometimes it will be unavoidable). One thing that the almighty ChatGPT recommended was to recreate the stuff I vibecoded, but write it manually, which is also an interesting avenue to take, since I know how it should function, but have no idea how to write it myself.

As far as the stack goes, you're spot on, going for react + node, which I think gives me the widest range for what I dream of building.

A big mistake I've made when I started coding side projects was that I was always trying to build a fully fleshed out app, with all of the features I wanted, right from the get go.

The problem with that is that my ambitious goals would take a super long time to make and I ended up never finishing most of my early side projects since I lose motivation and get frustrated trying fix and make everything perfect.

What I found to be a better approach is to focus on the minimal viable product, release it, and then keep iterating from there. Its nicer this way since you can make parts of your app and feel like you're making progress. And this also allows you to figure out quicker if a project is worth doing or scrapping.

So my advice is to focus on building the leanest version of your project first and then keep iterating from there.

SolicitingHamster said:

A big mistake I've made when I started coding side projects was that I was always trying to build a fully fleshed out app, with all of the features I wanted, right from the get go.

The problem with that is that my ambitious goals would take a super long time to make and I ended up never finishing most of my early side projects since I lose motivation and get frustrated trying fix and make everything perfect.

What I found to be a better approach is to focus on the minimal viable product, release it, and then keep iterating from there. Its nicer this way since you can make parts of your app and feel like you're making progress. And this also allows you to figure out quicker if a project is worth doing or scrapping.

So my advice is to focus on building the leanest version of your project first and then keep iterating from there.

Click to expand...

When I picture myself finally sitting down to work on something production-ready, I see myself exactly like you described yourself at that time - sky high expectations and the motivation to conquer the world behind my keyboard. I remember when I was taking my first front-end course and going through the advanced CSS section, for anyone else it might've seemed arbitrary, but I lost my mind trying to make my website look perfect, so much so that I eventually quit the whole course at that advanced CSS section. I finished it some time later, but I suppose it goes to show that trying to achieve perfection, especially at the beginning, can make you give up even at the seemingly easiest stage.

Solid advice, I appreciate it, and will definitely use it, thank you.

Surelis said:

I suppose it goes to show that trying to achieve perfection, especially at the beginning, can make you give up even at the seemingly easiest stage.

Click to expand...

Guys, I can tell you this: I have lost an awful lot of sleep over "perfection", nowadays I will take Good Enough and call it done!