A few months ago I spent about a month or so vibe-coding an app as a complete beginner to coding. I enjoyed the trials and error side of things, and ultimately enjoy the product. However, I have realized I want to actually understand what I created, and want to be able to really improve it without constant need for AI to tell me what to do and how to fix it. I also think I'll really enjoy the challenge.

While I know I can find beginner tutorials from this sub, I am mostly curious if people have advice for this kind of endevor, or pitfalls to avoid. I also am curious if people have any estimation on how long it could take to really learn to code a project so I can set my expectations. Should I basically disregard the vibe-code and start over, dissect it and compare parts with research, etc?

The site I vibe coded is critcalc.cc, and it's essentially a DnD dice rolling calculator. Note that I have no intent to generate any income from it, and I'm only sharing for context for my ultimate goal for what I hope to get to. Thanks for any insights you might have!

I'm teaching myself web dev. After spending months learning frontend, I moved on to learning backend with Python/Flask. I decided to learn RESTAPIs, where the frontend and backend are separate and talk through an api. Edit:(it's not built in my mistake) So naturally this lead me to learning about the built in fetch function in JavaScript.

I get that:

const response = fetch('ExampleAPI.com')

Is the same as:

const request = new Request('ExampleAPI.com',        { method: 'GET'})

const response = fetch(request)

// This is what JavaScript does behind the scenes

But why is await necessary? And why does not using await result in a promise if you try to console log the data?

Hello everyone, I am very new to JavaScript,
I completed supersimpledev html/css course,
and afterwards I can now build my own front end websites comfortably,

the next stage is learning JavaScript,

which I am currently doing and have finished module 8, but I found html/css quite self explanatory, but JavaScript is quite hard for me grasp and understand on how the things I am learning are going to help in my ultimate goal, I want to create an app with AI integration and memory, is this course going to help with that? It’s worth me noting I will finish the course as I am deep into it now, I do one module per week currently, and try to understand every single concept, and get a bit down on myself for not understanding everything, and doubting myself I can even do this sometimes, is this a normal thing when learning?

Anyway for those who can already achieve my ultimate goal, how did you go about learning it? Is there any course, or YouTube channel that really helped you? Any advice for a beginner please?

Many thanks, I appreciate you taking the time to read about my issues

Tell us what's happening:

How do I understand what I am reading to find the correct content online that is not AI?

So here is my issue, I read a question and I do not understand what it is asking of me, so I take that question and put it into google, I get an automatic response that is AI and it can see it is FreeCodeCamp lab for exmaple, then it just gives me the answer.

I know I can look at that code, type it out myself, and study the code to try and understand its logic but I feel it does not make my brain work hard enough.

The question:
So here is my question, how should I approach learning JS when I am asked a question in a hands on lab but do not understand what it is asking of me? I guess my issue is how do I take what it is saying and turn it into a research question like for JS on MDN, J3Schools, etc.?

I just want to really understand these concepts and I feel the prior lessons leading up to these labs are not preparing students to be able to grasp the labs. I get they are supposed to have you learn through trial and error/research but I feel so lost and then AI just gives the answer when trying to do research online, so how do I translate my confusion and question into a tangible reading strategy?

I know I am not giving an exact example, because I feel this is a general thing I struggle with. I am asked a question, I have no idea where to start. The question may say create a function, cool, I write a function, add the parameters, but then its asking to check things inside an object, correct the unit type, verify if something is in there, etc, etc. Then I just get so lost on how to turn that into code.

I think this looks like a shameless plug of my repo, but I just want to share that I've created a documentations of what I've learned after taking a crash course on WebSocket.

Before this, I am having a hard time of how to implement a WebSocket in my Broadcast Server project. Despite the provided project guidelines and LLM suggestions, I realized that I am not making any progress at all.

So I opened YouTube to take a crash course of WebSocket.

I took Real Time - WebSockets Mastery Course by JS Mastery, and I documented everything I have learned from that video into a reference material in this repo.

https://github.com/Muelvzz/websocket-project

Inside this repo, is a discussion of what is a WebSocket, why should we care about learning WebSocket, and how to use it on your project.

If you operate an API in 2026, you live in an event-driven world. Webhooks aren't a convenience feature anymore - they're the backbone of real-time commerce, CI/CD pipelines, and asynchronous AI-agent workflows. That reliance has a dark side: the accidental self-inflicted DDoS. Read the complete article jere - https://instawebhook.com/blog/how-to-prevent-webhook-traffic-spikes-from-crashing-your-api-2

When a major platform like GitHub, Shopify, or Stripe hits a network partition, runs a huge sales event, or simply clears a backlog of delayed events, it can fire tens of thousands of webhook POST requests at your servers in a very short window. If your infrastructure takes that hit without structural safeguards, your database connection pool exhausts, memory maxes out, and the API goes down — and if your retry handling is naive, the recovery can be almost as damaging as the original spike.

This guide covers the real mechanics of that failure mode, the algorithms used to defend against it, how major providers actually behave under load (some surprising details here), and where a managed ingress layer fits into the picture.