Hey Sup Forumsuys. I'm starting my 2nd semester of CS

Hey Sup Forumsuys. I'm starting my 2nd semester of CS
>inb4 fell foe the STEM meme
First semester was focused on discreet math and Object Oriented Programming (Java). Next semester I'm taking a data algorithms class that's used in C. I know I could just look up C and start learning. But what do you all recommend I do to learn it?

Other urls found in this thread:

gen.lib.rus.ec/book/index.php?md5=C684BE9C0147B68596683222502675FB
kat.cr/learn-c-the-hard-way-practical-exercises-on-the-computational-subjects-you-keep-avoiding-1st-edition-2015-epub-gooner-t11838564.html
hentenaar.com/dont-learn-c-the-wrong-way
twitter.com/NSFWRedditGif

install gentoo

Go to the class that teaches it

>8-space tabs
This meme needs to end

This desu senpai.

Doesn't teach it. Used to spend a week or two on it, but now you need to learn it over the summer so more class work can get done.

Read K&R.

8 space tabs are the best though. It lets you know when you're indenting your code too far.

Learn (and apply the concepts learned) the topics in pic related.

About half-way through the "Advanced" list, you can apply for a job.

A hard 80 character limit and 4-space tabs is a much better system.

This

Not this

I know all of those things by heart and I don't have a job.

The south-east asian jew is lying.

Two ideas.

K&R. If you already know a bit about programming this should be a breeze.

Find here: gen.lib.rus.ec/book/index.php?md5=C684BE9C0147B68596683222502675FB

Alternatively, Learn C the Hard Way, found here:
kat.cr/learn-c-the-hard-way-practical-exercises-on-the-computational-subjects-you-keep-avoiding-1st-edition-2015-epub-gooner-t11838564.html

This. Nowadays they hire anyone with a pulse.

You should fizzbuzz, OP

Time yourself too

"Learn C the Hard Way" is fucking awful

It taught me about makefiles, but it's really fucking awful otherwise.

>he couldn't learn C the hard way

Why don't you like it?

I learned C the better way. "Learn C the hard way" is literally just copy my poorly explained code: the "book".

Kek

Thx guys

shaw's method of teaching is grating and annoying
>copy this 500 line program
>now try to break it and tell me why it did that
>also, fuck K&R because [some stupid reason which i wrote a huge fucking article on which i later deleted and replaced with an even longer article on why i deleted the article]

>I know all of those things by heart and I don't have a job.
One of these statements is false.

People better than I have gone much more in-depth criticising it:
hentenaar.com/dont-learn-c-the-wrong-way

But my main criticisms is that he hardly explains anything and is some of it is factually wrong.

Where can I get a pure C job, mr. south east asian jew?

Thanks. Reading now.

Did you even read the article you linked?

>WAAAH I CANT INSTALL VALGRIND :((
>I'M A FUCKING ENGINEER!!!
What a fucking crybaby.

Embedded stuff, and firmware. I did not say that you should look for pure C jobs. I said that if you learn (and can apply) the concepts up to ~recursion, then you can apply for a job.

Yes, I read it a while ago.
>>WAAAH I CANT INSTALL VALGRIND :((
>>I'M A FUCKING ENGINEER!!!
He's writing the article from the perspective of someone completely new to C and maybe programming in general.

He's complaining because he assumes the reader has no motivation to google things?

For a book claiming to be a guide for something, "Just google it" is not a valid thing to say.

It's a guide to C, not a guide for installing a development environment to C.

Either way, I have to commend it for teaching make and valgrind right from the start because no other guide seems to do that and they're both indispensible for C work.

>not a guide for installing a development environment to C
You can't program in C if you don't have a development environment. You can't expect some complete beginner to know how to set that shit up, or what they even need.

If you're on linux, you don't even need to install anything but valgrind, everything is ready to use.

Writing C on windows or os x is a pain in the ass.

C in OS X is just as easy imho

I don't have any experience with OSX, but considering that it's a POSIX operating system, writing C is probably incredibly easy.

>outdated GCC from 2001
>apple distribution of clang doesn't even support openmp

I never said it wasn't feature-full, just that it's not a pain in the ass. I use clang, and openmp aside, it is still easy to use