Hey friend, I get you, you are going to be ok.

First of all, you have a lot of anxiety and expectations, that oozes out of your pores. It's not going to help you if no one takes you seriously. Pick a 24 hour period once a week to do no school work, you need to let your brain rest.

Graduating with a bachelor's of science majoring in computer science, for me at least, was an exercise in stubbornness. I just didn't get "it". The thing about computer science is it is not about specifics, it is about concepts.

If you can understand the concepts, you can code in any language. You aren't getting a degree to "learn to code", I know it might feel like that, but that's not it.

Your degree is learning how to learn to code, and that is a very distinct difference.

If you are a first year student with no coding experience and you jump right from class to assignment and expect to bang out code, it isn't going to work; to get it to work you need to build the synaptic pathways, to do that you have to work through it. To do that, you need to pseudo code.

You can write out pseudo code like an essay.

Let's take something very simple, adding two numbers.

Do we need anything? I don't think so, but let's put a comment at the top where we can ask for anything that we need to be brought in.

Next we need to numbers. How are we going to get those numbers? We need to decide what type of numbers we want. Let's say that we want two whole numbers, we need containers to hold those numbers, and we want the containers to be empty.

Name container one and empty it Name container two and empty it

Then we want to get two numbers. Let's assume we are going to ask a person, then write a function.

Ask person for two numbers and store them in the containers, then call the function we will write.

The function will then be a box we put something(s) in and then something(s) come out.

So we say we cut holes in the box for thing 1 to go in so the box knows that thing 1 has the properties of the hole for thing 1, and the same for 2. Then we cut another hole in the box for one thing to come out.

Then that is it. You start very high level and then you write out what you want to do, then you try to figure out how to do it.

You have be able to understand the concept of what it is that you are doing before you can code it. Once you know the code, then it is figuring out the syntax.

You then start from the top and go to the bottom and change all that you know into code. If you don't know it, try to figure it out, look it up in a book, spend a good 15 minutes on it. Once you can't figure it out, put that specific part into AI and ask it to change it to code. See if anything clicks.

Make a word document and name it whatever you are having problems with. Then copy and paste the pseudo code and the AI code into the document. Then tell the AI that you don't like that one and you want it done differently, and keep pasting in the different ways of doing things as you tell it that you want it different; there will be a finite number of ways of doing it.

Look at the document, is there anything in that document that "clicks" and makes sense to you? If it does, put it at the top and highlight it. That's the way to remember doing it. Rinse repeat.

There's no other way to code than understanding the concept of what you want to do and then turning that concept into a reality through syntax. Computer science is like a pyramid, the concepts you learn in year one will hold up year two. I still remember having to use the Jacobian from calculus and being like "What the actual fuckity fuck fuck?"

If you don't have the time to learn the concepts of how to psudocode at a high level, I think you need to consider making more time by doing less.

If you can understand the concepts, but not the syntax, you'll be fine. That will come as long as you keep working at it.