How many of you have gotten a computer science degree, but still don’t know how to code?

[-]

ScholarNo5983@reddit

The only way to learn how to write code is to by trying to write code.

At first this will seem very hard, if not impossible, but the more practice the better you will get. And you will need to practice a lot.

And notice I did not say watch lots of tutorials, since doing that will achieve nothing.

And one final point; learning to code has nothing to do with retaining information.

By forcing yourself to write code you'll find you naturally retain that information, without even trying.

[-]

ForeignOrder6257@reddit

This advice seems circular. “Learn to write code by writing code”. But how do you write code? “By writing code”. Enter infinite loop.

A much better advice would be to learn the process of writing code. A systematic process that is backed up with pedagogical research. Luckily for beginners, this process exists. It’s called the 7 step technique for translating problem into code. It can apply to any programming problem.

This is what beginners or anyone should get familiar with to help with writing code: https://adhilton.pratt.duke.edu/sites/adhilton.pratt.duke.edu/files/u37/seven-steps-comped19.pdf

[-]

ToeRepresentative627@reddit

Good lord people, just go write code! It’s like none of you have ever practiced and gotten better at something before.

[-]

MrKBC@reddit

That's hardly a fair comparison to make. Ballet dancers, opera singers, and musicians all start under the tutelage of a teacher who teaches them the fundamentals of their art form along with knowledge of how to practice properly without damaging themselves or their instrument. To chastise a layman for knowing how to go write code, practice code, or improve at something which they don't know how to even start - seriously? - is utterly demeaning. The majority of society don't even know what a terminal is let alone how to use it when the accidentally open it for the first time completely randomly.

[-]

ScholarNo5983@reddit

No one is learning to code by accidentally opening a terminal window.

They find a tutorial that shows them how to open and use the terminal window.

But guess what, if they only watch the video and never bother to actually open the terminal, they will have learned nothing, and none of the details in the video were retained.

They learned to use the terminal window by using the terminal window.

Likewise, you will learn to code by writing code.

[-]

MrKBC@reddit

At no point did I ever imply that people open a terminal window and instantly learn to code. Are you okay?

Parroting a video is quite literally the opposite of learning, but guess what? There's this foreign concept called "the written word" - in English given that's what we're using presently - that is so crucial to software development that their are entire courses dedicated to teaching it to anyone who's native language is not English.

The use of "terminal" was a mere reference to one of the tools used for writing code. Would you have preferred me to use IDE? Compiler? A notebook environment?

I commend you for attempting to make me look like a fool, but you failed rather tragically.

[-]

ScholarNo5983@reddit

The majority of society don't even know what a terminal is let alone how to use it when the accidentally open it for the first time completely randomly.

Here was you stating the bleeding obvious, in an attempt to sound like an intellect. That clearly failed, as its equivalence would be someone demanding their observation that pigs can't fly is a breakthrough in science.

There was no need for me to make you look like a fool as you managed to do that all be yourself.

[-]

MrKBC@reddit

Me? The fool? Honey, child, please.

My response triggered you, you chose to compile the most incoherent attempt at an insult with a vast majority of unnecessary syllables.

And since you chose to go right into insults, I don’t know why you’re reaching as hard as you are trying to label a portion of my response as an attempt at being an intellectual. I was dumbing it down for you because I knew you’d be so pressed by what I had to say based off your writing style alone.

You attempted to insult me and failed. Twice. Your attempt at refuting my comment failed. Twice.

I think we’re done here.

[-]

ScholarNo5983@reddit

I'm triggered. You're that feels the need to spout pages of word salad in an attempt to make a point.

I don't even bother ready your diatribe any more. It is worthless garbage.

Now watch as my reply triggers another response from you. Ha Ha.

[-]

MrKBC@reddit

You just defined yourself as an internet troll. Well played. Bye!

[-]

ScholarNo5983@reddit

Please come back. How will I cope without your amazing intellectual insights. I guess I will have to make do with the next best option which is watching paint dry.

[-]

MrKBC@reddit

So, what, youre Tinkerbell? Do I have to feed you insults instead of clap for you to stay alive? Not my problem.

[-]

ScholarNo5983@reddit

I'm really glad to see that I get under your skin. It shows your mental acuity is rather limited as it's a trivial exercise to fire a few of your limited number of synapses, to get you trigger. It's as difficult a task as pushing the button on the doorbell. But it is hardly sporting, as it is no more difficult than shooting fish in a barrel. It is such a trivial and exercise for me, I'm feel embarrassed for you. Do try harder.

[-]

MrKBC@reddit

You must live a very sad, lonely life to be so determined to keep this going. You’re the living embodiment of what society excepts someone who works with computers to be: bitter and jaded for absolutely no reason other than your own misery. I’m not even sure why you keep questioning my intellect - I’m rather set on my opinion that you’re just a lowbrow troglodyte - as we’ve clearly moved past that point. This is all really rather redundant since one of your previous comments stated that you couldn’t be bothered to even read my replies anymore as they were too wordy for your liking… and yet here we are.

[-]

MrTeaTimeYT@reddit

No you don't learn how to code by following tutorials. That's how you get stuck in tutorial hell.

You learn to code by starting a project that requires code, and then every time you don't know how to do something you go "How do i?" and then you look up that thing and answer the question for yourself.

Learning to program is just a very long series of "How do I?" questions.

That's how I learned to program when I was 12, sat down with the goal of making a video game so I went "how do i program a video game... oh ok i use C++... how do i use C++? oh ok I write a cpp file, how do i make it run? oh ok i download a compiler, ok it went hello world, how do i accept user input? oh ok i use std::cin" etc etc

Fast forward almost 20 years, and im still learning to program by asking those "How do I?" questions, its just instead of the things I don't know being basic syntax and semantic knowledge, its things like "How do I write a bootloader, never tried that hmm"

[-]

ForeignOrder6257@reddit

How about a video tutorial that shows people how to do exactly what you wrote here, seeing run into and solving a series of “how do I?” Questions. Now THAT would be a valuable tutorial, not other tutorials that just give you the code

[-]

MrTeaTimeYT@reddit

Yeah that would be a valid tutorial structure.

Some like dora the explorer "Can YOU see the problem here" pause for timer so you can figure it out.

I just worry that people would "cheat" the learning process, its kinda like giving people the answers in the back of the book, if theyre treating the test like something they just need to checkbox they're just gonna read the answers right.

[-]

MrKBC@reddit

Well said.

[-]

rawbdor@reddit

The implication of the question, though not directly stated, is that OP has gotten a computer science degree and still doesn't feel confident in his ability to code.

If that's true, then OP already has "started under the tutelage of a teacher who teaches them the fundamentals of their art form, along with knowledge of how to practice properly".

And at this point, OP just needs to go write code.

[-]

MrKBC@reddit

To paraphrase my response to the comment referenced above, I'm not concerned with OP and their lack of confidence in their ability to code. The purpose of my comment was to subtly and less-than-politely point out that the respondent to OP has chosen a verbiage comes across as condescending, elitist, and ignorance. Thank you for your dissection of my comment, however, but you assessment unfortunately missed the mark.

[-]

rawbdor@reddit

Thank you for your reply. I disagree with your assessment that the respondent to OP had chosen a verbiage that came across as condecending, elitist, or ignorant. I believe the respondent to OP recognized that OP had, in fact, already trained, and now needed to go write code.

As I read it, the respondent to OP wasn't suggesting that untrained individuals simply go write code (though my personal opinion is that, even for untrained individuals, "go write code" is a perfectly valid task, as I did it myself when I was 10).

I believe that your assessment of the respondent's comment misses the mark by a wide margin, on context, tone, and feasibility.

[-]

MrKBC@reddit

Thank you, bot, go on now.

[-]

rawbdor@reddit

lol, get fucked

[-]

MrKBC@reddit

Aw, human like response! Well done, ya cunt.

[-]

Hei2@reddit

is utterly demeaning

No, what's demeaning is what OP (and his college) has done to computer science degree owners everywhere. OP has already earned a degree.

[-]

MrKBC@reddit

Yeah, I'm not concerned with OP. He's got his own shit to sort out. My point is that you find it acceptable to speak to someone - whether in person or not - is borderline ignorant. I'm only going with benefit of the doubt that you're not ignorant since you've developed the superior human skill of writing code. I only say superior because your response to OP not only implies that you're better than those who can't write code, but the fact that you've subjected the context of my response to you as implying that we should "hand hold" any college graduate screams much more than simple ignorance.

[-]

ForeignOrder6257@reddit

Yes, you're right, go write code. But students need deliberate practice. They need to be taught how to write the code. Whether its from tutorials or instructors that's the starting point, then over time they naturally absorb the knowledge and will then have better chances of writing code on their own. So i wouldn't say watching tutorials is useless

[-]

ScholarNo5983@reddit

From your link: "Students in introductory programming courses struggle with how to turn a problem statement into code."

The reason students struggle to do this is because they have no idea about the basics of programming.

For example, I would assume most who struggle would also struggle to explain how a simple "hello world" program actually works.

And because they struggle with something that simple, they also struggle with other basic programming concepts like control statements, variables, types, functions etc.

Now when you're missing so many basic skills, how would anyone expect them to also be able to find a coding solution to a given problem.

But naturally you don't just start coding and then keep writing more code. You start with a book or a video or a tutorial or a programming reference manual and then you try to write "hello world". That could take an hour, a day or even a week for some. But it will be time well spent.

Then add some user input to your hello world program; add some for loops; add some if statements; add some integers and floats and doubles; add something from the programming reference manual and at every one of those not only get the code to work but understand how the code actually works.

Before you know it, you've produced a few pages of working code and without even trying programming details are starting to stick.

Naturally this does require a level of skill of the participant, and many will struggle to do this. But there is a reason 13-year-olds can teach themselves to write code. If you have the right mindset, it is doable.

But even after a month of doing this, you will have only learned the most basic of programming skills, and you will still face many years of more learning. But at least you'll now have a basic understanding of at least one programming language and have an ability to write and understand simple code.

Naturally there are numerous ways to learn programming, but this approach is a tried and tested method of learning to program. It works (for some).

[-]

Ok-Luck-7499@reddit

I watched a lot of videos and remember close to silch

[-]

FreeGazaToday@reddit

computer science != "coding"

[-]

ScholarNo5983@reddit

I do realize Computer Science is much more theoretical and mathematical than Computer Engineering.

But is it common for a Computer Science graduate to have absolutely no ability to write code?

That seems rather strange to me.

[-]

dumpin-on-time@reddit

computer science and computer engineering are verrrry different. do you maybe mean software engineer?

i might expect a computer engineer to know assembly but wouldn't expect him to be fluent in any high level languages or know anything about software paradigms and principles

[-]

ScholarNo5983@reddit

I'm just asking a very simple question.

Is it common for a Computer Science or a Computer Engineering or a Software Engineer to graduate without the ability to write code?

I would have though all these graduates would have at least a basic ability to write code.

computer engineer to know assembly

Anyone who is good at assembler will most likely also have at a minimum working knowledge of the C programming language. And anyone with a working knowledge of C should find it easy to pick up at least a basic understanding of other languages.

[-]

dumpin-on-time@reddit

I'm just asking a very simple question.

you're not though. you don't even understand the words you're using

a computer engineer designs hardware and the industrial processes to build them. "coding" isn't that relevant to their core worth. it's an added bonus but not their core skillset

a computer scientist is closer to a mathematician. they can likely write code, but it's probably trash from an industrial perspective and not why they would be hired. anything they write will be rewritten

I would expect a software engineer to be able to write code, but the title "engineer" is loosely thrown around and usually has nothing to do with engineering. developer, engineer, progammer, coder, they all mean the same thing and nothing at the same time

Anyone who is good at assembler will most likely also have at a minimum working knowledge of the C programming language.

probably. maybe at one point in time. that divide is broadening though. how helpful are a bunch of low-level bit shifts in most cases? The team building C has to know assembler/assembly but not the other way around

And anyone with a working knowledge of C should find it easy to pick up at least a basic understanding of other languages.

hypothetically, sure, but in reality it ends up looking like people who dont know a language forced a language to be the language they know. language development is a matter of socialization, politics, nuance, and creativity. there's no inherent link between ASM and C. there were many languages before C became the de facto lowest-level standard above assembly

in short, CS graduates generally suck at writing code, if they can at all. programming is a blue collar skill. CS is not. most software jobs require the former, not the latter

[-]

ScholarNo5983@reddit

in short, CS graduates generally suck at writing code, if they can at all. programming is a blue collar skill

Clearly you have no idea what constitutes a blue-collar job.

That lack of understanding renders the rest of your word salad nothing more than a meaningless ramble.

[-]

dumpin-on-time@reddit

trade craft? does that make you feel better?

just because you're offended doesn't make you right

and to repeat, no. CS grads can't write code

[-]

ScholarNo5983@reddit

You're an idiot. It's a white-collar job. How out of touch of the real world are you.

and to repeat, no. CS grads can't write code

Let me correct that for you. Useless CS grads can't write code.

[-]

dumpin-on-time@reddit

I'm sorry you're offended. that doesn't make you right

Let me correct that for you. Useless CS grads can't write code.

the question was about whether it is common. yes, it is very common. I've been interviewing, hiring, and mentoring developers for over a decade

[-]

ScholarNo5983@reddit

I am in no way offended, and in fact I feel sorry for you. You seem to have a very limited ability in comprehending the written word. It must be difficult living with these kinds of limitations. Add to that what appears to be a chronic case of total delusion of self-righteous grandeur, I can see why everything you write ends up as long-winded, word salad rant about nothing of substance. This is sad to witness firsthand.

[-]

dumpin-on-time@reddit

sure, you're so not offended you feel the need to insult. that's exactly how people who aren't offended act

[-]

ScholarNo5983@reddit

You're as bad at understand computing technologies as you are at reading humans. I am in no way offended by anything you've said. I just find it really enjoyable highlighting out your many failings. Keep it up, this is so much fun.

[-]

dumpin-on-time@reddit

they're disciplines, not technologies

[-]

dmazzoni@reddit

That's true, but 99% of people who get a CS degree go into a field of software engineering.

The demand for theoretical CS researchers is small.

Yes, CS leans a little more theoretical, but the goal is to understand how computers work - and more broadly how computing works - so that you can solve problems using computing - i.e. by writing code.

Colleges should NOT be teaching things like today's popular frameworks. Those change.

But colleges should be asking you to code a lot. And in my experience, they do. The only thing that's changed is that now it's easier to cheat.

[-]

grismar-net@reddit

I knew how to code before I got a Computer Science degree, but I'm fairly certain I would not have learned to code from my Computer Science education. Many people who graduated alongside me definitely could hardly code at all. And to be clear, that's not a complaint - Computer Science isn't intended to teach people how to code.

Of course programming is part of the curriculum, because it is how software and firmware gets made, and a lot of the theory of CS is about programming. But just like you don't have to be very good at sports to become a sports physician, you only have to know enough about coding to be able to do the science.

Vocational schools or colleges that teach programming do a better job of teaching people how to code, because that's what they're supposed to teach. A CS student can get away with Programming 101, Functional Programming, Compiler Design and maybe some stuff like lambda calculus and declarative programming and that'll be that.

To be clear, you *can* of course specialise in Software Engineering and get your CS degree by stacking your roster with programming-related courses. If you pair that with actually doing a lot of programming in your spare time, you probably come out of your CS studies as an excellent coder. But it's a specialisation. If you pick the easy courses, or the interesting ones that have nothing to do with coding, not so much.

[-]

Middle--Earth@reddit

I used five programming languages on my computer science degree. It was hard to avoid coding, so I'm puzzled by these comments saying that it isn't a good degree to pick for learning to code.

[-]

grismar-net@reddit

If you reread my comment and make it to the end, you'll notice that I say you can come out an expert.

I'm saying that a degree in CS is not guaranteed to make you a good coder and you can come out with a degree and not be able to code well at all.

I was taught Modula (imperative), Miranda (functional), Prolog (declarative), Java (as part of a software design course), and C (as part of Compiler Design), and my Expert Systems class used Lisp. (this dates me to being in uni during the 90s - but I still follow and support classes today)

But most of those classes taught paradigms, design principles, applied logic, etc. The languages were there and those of us that were interested would pick them up, but to pass the course, you'd only need to know them well enough to pass assignments that used them, not actually learn to program well in any of them.

[-]

Middle--Earth@reddit

There's no need to be pompous.

I just pointed out that the particular degree course that you chose to pay for may have been light on coding, but that's a choice you made and wasn't a typical experience. With many CS courses (at the time I studied) I saw that it was hard to take a module without a coding element to it

You get what you pay for, and also you get out of it what you've made an effort with. You're meant to treat the course as a full-time job, so you're meant to be studying and coding when you aren't in lectures, and spend around 37 hours a week minimum working on all of it.

Degree courses aren't intended to teach you coding in depth. They are meant to give you a reasonable foundation in the language, and then you diversify into the part that interests you more, and then you teach yourself a deep dive into it. If people aren't motivated enough to get as much out of their degree as they can, then that's more on the individual than the course.

[-]

grismar-net@reddit

I went through a full bachelor and master's degree program of 5 years (actually taking 7 due to other activities and courses taken) and then stayed for a few more years, teaching and working in the city.

"Pompous"? I think you need a reality check mate. And I really do think you should read a comment before responding to it - it's clear that you don't, repeatedly.

[-]

Middle--Earth@reddit

Sorry, I meant pompous and rude with it, because there's no need to make assumptions and respond in such a way when someone has a different opinion to you.

Try to show a bit of respect to other Redditors instead of talking down to them like that.

[-]

gamer_mastermonk@reddit

I went through 3 years of college without learning to code anything. I was so scared of not getting a job because I didn't know anything.

So I researched for hours on what might be the best resources to learn and crack industry interviews.

I learned that most resources are really good but what matters most is - is it friendly enough that you will stick to it and does it have a proper curriculum/path that you can follow instead of having 500 courses and having to choose next course every single time.

Finally I decided on the Odin Project for the frontend (completely free) & boot.dev for backend (free to read but I love their paid interactivity)

So I started with boot.dev because I felt their interactivity keeps me coming back. It took me 12 months just to complete the backend path, but I learned so much & it built my confidence up that I could easily work at any job I get.

I started applying, it was quite difficult in this economy last year & finally was able to get a good paying remote junior developer job.

I make a little more than my dad who has been working in his job for the last 26 years. It's crazy how rewarding a career in software development is.

Good Luck!

[-]

kyzfrintin@reddit

I mean this seriously

How the fuck did you get your degree without actually learning anything?

[-]

StinkButt9001@reddit

Comp Sci degrees really shouldn't have too much hands-on programming. That's what software engineering is for.

Comp Sci is more focused on math and abstract concepts surrounding computing.

In my CS degree, the only code we wrote was to demonstrate concepts we were learning in class. Like code to traverse and manipulate graphs and other data structures. We were expected to know the concept we're working with more than we were ever expected to know how to actually write (good) code.

[-]

paranoid_throwaway51@reddit

imo i hate the idea the line of thinking about "oh computer science isn't really about computers its about abstract & discrete mathematics"

in my experience its always been spewed out by incompetent teachers trying to reason with the fact that they can neither program nor do much mathematics.

[-]

minneyar@reddit

It's literally true though. Computer science is the study of the theory of computation. You can do it without ever touching hardware at all. Programming is just a tool used to study computers, like telescopes are to astronomy. If you want a degree in programming, you want software engineering, not computer science.

[-]

paranoid_throwaway51@reddit

https://www.collinsdictionary.com/dictionary/english/computer-science

"the science that deals with the theory and methods of processing information in digital computers, the design of computer hardware and software, and the applications of computers "

[-]

Middle--Earth@reddit

My computer science degree was heavy on coding, and used five programming Languages.

[-]

IrishPrime@reddit

Same. For example, we had a class titled Data Structures and Algorithms. I think this is a pretty standard course in a CS degree program. The associated labs and homework assignments for the class required us to implement a bunch of data structures (in Java) and then use those data structures in the implementation of various algorithms.

If you passed DSA, you were pretty much guaranteed to have sufficient experience to implement a bunch of different sort, search, or traversal algorithms for trees (binary search trees, B-trees, red/black trees), graphs, multidimensional arrays, etc.

I had a class on Operating System Design, in which we learned about threading and had to write some simple multi-threaded applications to demonstrate we understood the material.

Networking? Implement HTTP and TFTP servers, then BGP routers.

Compiler design? You guessed it, implement a compiler.

None of this was big enough to really count as software engineering (besides the compiler). We spent a bunch of time on theory, but to prove you understood the theory, you had to implement it.

I've heard a bunch of people online claim that a real CS degree generally has no coding at all, but I've never met a person in real life who got a CS degree without having to write a bunch of code as part of their coursework.

[-]

disappointer@reddit

If you told me you had a degree in astronomy from but didn't know how to use a telescope, I would have some questions.

[-]

MrTeaTimeYT@reddit

That's the thing though, if you went and took an astronomy degree, there are no classes on how to use a telescope.

Because strictly speaking, you dont actually need a telescope to practice astronomy, you only need the data that comes from that telescope. And that's the bit they teach, how to analyze and understand that data.

[-]

Sector-Difficult@reddit

Cheat on exams and do all the assignments with ai seems to work for some of my classmates so far

[-]

jam_pod_@reddit

I’ve known plenty of CS degree-holders in the-LLM era that couldn’t write working code to save their lives (or at least their jobs)

[-]

csprofeddie@reddit

CS prof here. Can confirm.

[-]

conventionistG@reddit

Damn, even the profs are cheating and using ai?

[-]

Striking_Rate_7390@reddit

in todays era the student really dont learn anything if he/she is passionate about it !

[-]

deleted_by_reddit@reddit

[removed]

[-]

AutoModerator@reddit

Please, ask for programming partners/buddies in /r/programmingbuddies which is the appropriate subreddit

Your post has been removed

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[-]

deleted_by_reddit@reddit

[removed]

[-]

AutoModerator@reddit

Please, ask for programming partners/buddies in /r/programmingbuddies which is the appropriate subreddit

Your post has been removed

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[-]

ScholarNo5983@reddit

It would seem this is now a common approach to learning these days, but in the end that approach will end in disaster.

There are no shortcuts.

[-]

Ok_Court_1503@reddit

AI

[-]

dumpin-on-time@reddit

you've clearly never had to interview anyone or work with a new hire. unless working in the specialized area of their thesis, recent grads are about as useful as a hobo doing Todo App tutorials on Medium

[-]

Lanyxd@reddit

Most university/college courses for programming is basically an online tutorial you can ask questions directly. Most students don't go out further than exactly what they are told to do.

[-]

Swing_Right@reddit

In my senior year (before LLMs) I had to teach a classmate how to use the Python REPL and write basic python code for our senior project in which they were my group member. I don’t think they knew how to code at all. They were trying to write python code directly in the terminal and didn’t know why it kept saying command not found 🙃

[-]

JohnBrownsErection@reddit

Liberty University accepts donations in lieu of skills.

[-]

spongeysquarepantis@reddit

Me

[-]

arthoer@reddit

With a computer science engineer degree you are an engineer right? Not a developer. So leave the developing to the developers and the engineering to engineers. You give me some architecture ideas, I will translate it into working software.

This is one of the problems the software development market has, almost uniquely to the US. Where engineers apply for a web development job at Facebook or something. Then they become a master of a button and think they are doing well. Suddenly they get pipped and they don't understand why.

Similar to companies who think you need an engineering degree to do development.

Linus Sebastian andJohn Carmack dont have a computer science degree. /shrug

[-]

mxldevs@reddit

I don't understand, are some schools not requiring CS students to be able to write code?

My first two years were full of coding alongside theory. If I couldn't submit working applications and write entire algorithms with pen and paper I was not passing those courses.

Or did you just let AI do all the work?

[-]

magick_bandit@reddit

Put down the AI, build things.

It’s incredibly simple and yet difficult for most.

It’s absolutely normal to be stuck for weeks on a concept.

[-]

Ok_Court_1503@reddit

I don’t have a comp sci degree and have a mid career sw dev job at an F500 company for the flip side of the spectrum

[-]

povlhp@reddit

I can code since I was 11 or 12 but demand was too big so never finished university. No degree. There are some modern languages I don’t know. Go and Rust are examples. But then I have experience with assembler, low level C , forth etc

[-]

dumpin-on-time@reddit

programming and computer science aren't the same things. one is a tool. the other is a.. science

sure, there is significant overlap, but many things were proposed long before computers existed, and many things that are programmed have nothing to do with computer science

there's a divide between theory and the nitty gritty. right now the gap between cs and programming is very narrow. but it's the same with all other engineering and science disciplines. draw a straight line. build a cube. those are conceptually simple, but if you actually have to build your own tools, it's not as easy as it seems. if you've been building things for a long time, you don't have to think too hard about it

programming takes repetition and muscle memory. once you get that, you'll be able to work on ideas, not the basics

[-]

OutrageousInvite3949@reddit

What’s sad is I have a degree in religion and I have programmed games like Tetris and basic Minecraft like games in c or c++ or even done projects in python, or Java

[-]

nullptr023@reddit

everyone has its own way of learning. To learn it, you need to understand each line of code you are writing and NOT JUST COPY PASTE. Keep doing it and it will be muscle memory. Also, writing code is not about memorizing the syntax. It is more like problem solving. Also, when you learn a concept, try to apply it in your project or maybe look for exercise that apply that concept. Keep doing it and you'll eventually recognize the pattern.

[-]

Siegorvus@reddit

Go on leetcode start burning, you don't use it you lose it.

PERSONALLY, I forget steps myself but it's like riding a bike, you pick it back up as you go along,

Download Unity and start making a game, look at minecraft and start making mods, hobbies like these can help you retain your skills. I do these because they don't bore me to death trying to make some mindless project.

[-]

patternrelay@reddit

Yeah this is super common, tutorials feel like progress but they don’t force recall. What helped me was building small dumb projects from scratch and getting stuck a lot, that’s where things actually stick.

[-]

No_Report_4781@reddit

Have you tried upgraded your hard drive? It sounds like you’re overusing RAM, and not writing anything to long term storage.

[-]

Unlikely_Studio_5115@reddit

fr tho

[-]

bpalun13@reddit

Don’t even use an IDE to practice at first. Start with just notepad. Write pseudocode. If you know the syntax of the language you are working with, then start writing. If not start searching the docs for the syntax you need to bring your idea to life and get building. Once you have a good chunk of work done, go ahead and copy it into your IDE and get to testing and debugging.

If you are not understanding the function or the why of a piece of code you write, ask AI to explain only, do not have it give you any generated code. Use AI to help you understand, not create.

[-]

dkopgerpgdolfg@reddit

While your question doesn't apply to me, I'd like to remind that "computer science" is not the same as "creating software".

[-]

Amazing-Mirror-3076@reddit

From recollection, 2/3 of the class.