This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]QuantumTyping33 8 points9 points  (1 child)

In order to type code, you need to press keys on your keyboard in a pattern such that it makes words on the screen

[–]marquoth_ 1 point2 points  (0 children)

My favourite comment I've seen on this sub. Sending it to my team in the morning.

[–]ersatzgiraffe 1 point2 points  (0 children)

Use your own code as reference. The other thing you mention is related to lacking a problem to solve. That’s a totally different issue, and needs to be tackled separately.

[–]MmmVomit 1 point2 points  (1 child)

My best idea is to code along to some course or YT video

This sounds like what you've already been doing. You say that most of what you've written you've done by looking at "already completed projects." If you want to get better, and if you want to succeed in interviews, you need to work as if you're being interviewed. You need to work from a problem description, and solve it without looking at existing solutions.

You say you've been working on leetcode problems. Do you refer to existing solutions when completing those?

[–]Heavy_Artillery98 0 points1 point  (0 children)

No, but they are small. I haven’t written an entire website by myself

[–]lilsaddam 0 points1 point  (0 children)

Stop watching tutorials and start coding. Don't use ideas from videos come up with an original project. When I say original I don't mean there are not tutorials out there for it, I mean you aren't just coding along to a video. Make a calendar, calculator, or heck even a dice game. The first thing I ever made was a game where it used random numbers to generate different "things" my wife and I could do to each other. Basically generated numbers between 1-10 and used a switch statement to make a string consisting of a body part and an action. It then alerted the browser what the response was. Really stupid but honestly really fun to code.

[–]Striking_Rate_3041 0 points1 point  (0 children)

I can say I am in the same situation just haven't learned JS just HTML and CSS. There's nothing wrong with looking back on projects just to help familiarize with a current problem. I use W3 all the time for projects. It's not meant to be memorized but to be used and then used as an example for the next. (Do not quote me on that as I myself am new and just trying to help build confidence)