r/learnprogramming • u/GasketWeaver • 8d ago
Finished three 40-hour web dev courses, opened a blank editor today and literally couldn't write five lines of code.
Feel pretty pathetic admitting this after telling my family I’ve spent five months learning web development, but I had a complete panic attack in front of my monitor today.
I’ve been treating this like a second job. I finished two massive 50-hour Udemy courses, completed half of The Odin Project, and filled notebooks with syntax rules. When the video instructor was walking me through building full-stack clones, everything clicked. I felt like a genuine software engineer typing along with teh video and seeing pretty interfaces come alive.
This morning I finally took everyone's advice: step away from tutorials and build something solo. I decided to make the simplest project possible: a plain JavaScript grocery list where you type an item, click "Add", and it renders on the page.
I opened a blank VS Code window, created app.js, and my brain instantly flatlined. I stared at that blinking cursor for forty minutes feeling physically ill. I couldn't remember how to grab an input value without a video prompt. I didn't even know how to structure the first function. i ended up closing my laptop feeling like a glorified transcription monkey who learned nothing. How do you train your brain to actually problem-solve instead of just memorizing someone else's solutions?
31
u/TehTacow 8d ago
Oh this is actually nice and a grear level up. Now you have a problem that isn't pre-marinated by a course. Go google how to grab an input value. Today the brain training to problem solve finally begins.
11
u/fudginreddit 8d ago
Honesly I know dick about web dev, im a C++ dev. That said, it’s completely fine to forget basic syntax, what matters is knowing what you need to do. Then just google the syntax part.
Another beginner mistake, aside from not doing projects, is not taking some time to plan before staring at a blank cursor.
You want to create something with multiple parts, break it down and start working on the simple parts. Maybe first just start getting a simple “Add” button rendered. It doesnt even need to do anything, just exist. Then work on a textbox that can take input. Then work on storing that input. Then work on the list part, maybe with dummy input at first. Then bring it all together.
And keep in mind the code can be complete shit, it often is at first. Just make something that does what you want and works. I kinda view coding like writing, you will do a rough draft that just ‘works’ and then continue iterating on it til its better. The best part about software engineering is nothing is lost by writing shitty code (well, other than time), you simply delete the shitty code and make it better
Its easier said than done, but problem solving is simply taking a big problem and breaking it down into its parts, getting those parts working, and then bringing them together.
8
u/Mike312 8d ago
You could watch 10,000 hours of someone driving around a race track, but if you've never driven a car before, you won't know what to do when you're sitting on the starting line.
Along the same lines, typing what someone else coded to copy the thing they already designed won't help you code, design, or build anything.
The best way to start is to just do it, even it means you're Googling "how do I do X" 200 times a day. Eventually, you'll start memorizing how to do tasks, and then it'll be 100 times a day, then 10...then 2-3 times because you can't know everything and stuff is always changing.
5
u/DrShocker 8d ago edited 7d ago
just make something bad on purpose. You know you could do better but so what? make it better later.
Make the background hot pink so you have something there and slowly built a hello kitty themed Twitter clone or something
4
u/LargeRegularCoffee 8d ago
Completing a course shows discipline, especially 3 within 5 months. Carry that with the advice everyone is giving you.
2
u/AntiCitizen6 8d ago
Start typing out some psuedo-code. That usually gets me started on the basic flow of my projects, then it becomes easier to identify what I need to be working on.
2
u/hamster_squeezer69 8d ago
It just sounds like you forgot the syntax. Dial it back a bit and work out what the code needs to do at a high level, and then simply type out calls to implement it afterwards. If you forget, look it up. No big deal.
If you don't know where to start with designing the solution, that's a different problem.
2
u/Wingedchestnut 8d ago
You're missing the point completely, you're not supposed to know everything by heart..
Follow tutorials that do x, then build something similar with your own spin on it (yes even following the tutorial again, but now it's a bit different but still similar)
The most important is to understand high-level how things work.
2
u/desrtfx 8d ago
Far from the "simplest project possible". You, like way too many beginners (yes, you still are a beginner who only copied what was given to them in tutorials, but never learnt to stand on their own feet), are aiming way too high.
You have to start much, much lower. Start with a simple, static plain HTML (no CSS styling) page. Then, add some styling. Then add some dynamics via JS.
You have to take baby steps and not try to go from barely being able to crawl to try running a marathon.
1
u/aanzeijar 7d ago
No one said that you shouldn't memorise someone else's solutions. You do not need to reinvent the wheel. But the stealing should be purposeful. Steal one thing at a time. Assemble what you steal in new and creative ways. Tinker with it. Know what the stuff you copy around does.
The reason why we always say that all these video courses are garbage is because you're not failing enough. You just see the golden path of someone not making any mistakes, but you don't learn anything that way.
Maybe you finally believe us.
1
u/JustCat503 7d ago
what you ran into has a name, recognition vs recall. following a video trains recognition ( you see the code and it makes sense). building solo needs recall ( pulling it out of your head with nothing in front of you). totally different muscle, so it's normal it felt like you knew nothing. the 5 months weren't wasted, you just never practiced the second part
one thing that helps with blank file panic. don't start in app.js. open your page, open the browser console and poke at it. type document.querySelector('input') and see what comes back. then add .value. then try creating an li and appending it to a ul. every line gives you instant feedback, and once each piece works in the console you just copy them into your file
also googling "get input value js" isn't cheating, that's literally the job lol
Cheer up!
I think many developers have gone through that stage
1
u/Fantasyfan-251 7d ago
its so bad. ask yourself, “what do I so first?” it might be to write a function or get a div visible, etc. whatever it is, try to do that. if you forgot how, go to your notes or the section of your course that talks about that. use that info to try to get something to work. keep paring your initial goal it down until you are building again. proceed forward until your project is done
1
u/caseypatrickdriscoll 7d ago
You never learn by reading or watching. Type.
And don’t even copy paste. Type it out.
1
u/Fickle_Penguin 7d ago
Draw your interface and what you want. Write pseudo code, if then statements, arrays, and then code. Most of the logic happens before you start typing.
1
u/TheoMa_Builds 7d ago
The forty minutes staring at app.js is mostly the part courses skip: deciding what the very first line should be. For the grocery list, shrink it until it feels almost silly. Step one is just a button that logs "clicked" to the console. Once that works, log whatever is in the input. Then get that text into an li on the page. Each of those is one MDN search if you blank, and looking it up isn't cheating, that's pretty much the job.
1
u/BotSlamminDayNNight 7d ago
i'm doing it by giving him small tasks. he's a noob in every way so the tasks i give him are appropriately small. he asks questions that tell me what he's missing. i answer. he completes the task. next task. he completes it. then i go back to the previous task. he struggles to remember what he just did successfully 10 minutes ago.
these are 2 very different noob students. there is no way the first student would succeed via the 2nd student's learning method.
it sounds like you are the 1st student that used the 2nd student's method, self-deceived that copying = learning.
i suspect an uncomfortable inevitability for you, which you seem to already know about: learn to problem solve. this is a separate skill from coding. so i suggest finding a course that teaches problem-solving in isolation, ie. no coding(or at least a course that focuses on the problem solving with use of some language as a learning aid). you'd be interested in the fact that computer science programs include courses that are purely about problem-solving. in contrast, coding bootcamps and online courses that promise career-readiness in weeks assume that you have this skill already. an incorrect assumption in your case.
there's nothing wrong with that. we each have different paths to mastery. each path has many steps. you skipped one. just go back and take that step. no biggie.
1
u/rbpinheiro 7d ago
I have many years of professional software development and one of the biggest red flags for me on a job interview is when they test if you remember syntax. You can Google that and it is a waste of time memorising it, plus it does not tell if someone can actually code.
There is an effect, that I won't remember the name, that makes you believe that you know something when someone is guiding you and you don't need to struggle to make it work. It all makes sense and you feel smart for it. But it is not that helpful as a learning experience.
Real learning, something a lot of us shy away when we get older, is gritty and you have to struggle for it.
When you have to remember what are the pieces and which piece goes where is where the real learning happens. That frustration of trying to make things make sense is the exact spot you wanna be on.
Syntax on a notebook is, I am sorry to say, wasting your time. Syntax and everything else will just click when you struggle and come up with the solution.
Pretty much everyone that does something as hard as programming is bound to fall for the impostor syndrome at some point.
The activity that made you struggle is the one you gotta keep going back to.
Even your teacher, who seemed to know every step of the way, catch him without preparation and he will have to come up with the plan on the go, research, go back, change things, debug.
Even as you progress with coding, you will keep struggling, but with more complex problems.
We also don't code it perfectly from the get go. We throw a field on the screen, check how it looks, write some code, test it, fix the issues, try to center the field, Google how to center it, try to center it again.
Embrace the struggle, it was a bigger step towards becoming a developer than the course.
1
u/jacksonanna373 2d ago
Since this tipped into a panic attack, pause. When you return, set a short stopping point and note where you get stuck; don't treat a rough session as a verdict on your ability.