Honestly, How I Learned Was Via Make.

Honestly, how I learned was via make.

Like... you can easily find compleatly incomprehensible make files that automate everything.

Those you can use, but they are not how you learn.

How you learn iz by doing it very very copy-paste of the lines toh would write to the compiler in a shell. Most basic one with a single .c file would be:

gcc main.c

Then figure out what arguments to add to it to make it how you want. Name the output file. Have the source file in a different folder. Have the ouput be in a different folder.

You now know how to compile a single file by using a shell

Now. Create a make file. Simply have it call exactly the same thing you wrote in the shell before.

Then figure out how to compile a main file and a file with functions and a header. Again, first just by using a shell. And then build it into your build file.

This is not too hard. There are plenty of guides and examples. It is fun exploration where you get your hand dirty and you will learn a LOT about how coding projects and IDEs work.

A programming IDE is just a text editor and make file builder with a pretty GUI on top

It is not magic. And it is not even that complicated.

Sure. Automating it and making it solid and taking all the things that may change into account so it can be generic is hard

But creating a make file that will compile YOUR project? Not hat bad.

never learning how to properly handle multi file c projects is finally catching up to me and stabbing me to death with linker errors.

"If voting changed anything they wouldn't let people do it-" grabs your face THEY DIDN'T JUST "LET" PEOPLE DO IT, MOST PEOPLE COULDN'T VOTE FOR HUNDREDS OF YEARS. PEOPLE OF COLOR ONLY GOT THE FULL RIGHT TO VOTE 50 YEARS AGO IN THE US, THATS BARELY A GENERATION.

IF IT DIDNT MATTER AT ALL WHY WOULD THEY SPEND SO MUCH TIME GERRYMANDERING THE SHIT OUT OF EVERYWHERE?? WHY CAN'T FELONS VOTE?? WHY CANT PUERTO RICO VOTE? WHY DO THEY KEEP SWITCHING DATES AND LAWS AND TIMES AND WHATEVER THEY POSSIBLY CAN TO STOP PEOPLE FROM VOTING?? WHY DO THEY MAKE EFFORT AT ALL??

BEING DISILLUSIONED IS A REASONABLE RESPONSE. BUT PEOPLE FOUGHT AND DIED AND ARE STILL FUCKING DYING FOR THAT RIGHT, DONT SPIT IN THEIR FACE.

Ehhh.

Both have their pro's and con's

I DEFINITELY have bands and records I listen to because I know I like 100% of what I will hear.

But since I also want unusual and strange music, I sometimes find bands where I like 1-3 songs only.

But I WANT those bands to make the songs I do not like. They are part of the proccess of making the things I like.

Cannot get good art if there is no tolerance for bad art

"There's nothing rarer than liking every song on an album" y'all are listening to the wrong albums

If the coding convention is not enforced with auto-formaters, it does not exist. If someone wants all the code to be written in exactly the same way every time... then get a machine to do that. Doing the same thing every time is what computers are good at. Set up a autoformater. If that is too much work. Then they have just said it is not very important, which means it is not very important. What IS very important is to make your code readable. Developers spend ~80% of their time READING code. So make THAT part easier. The code should fulfill its functional and performance requirements, after that, it should be made as easy to read as possible. It should take the reader from high abstraction overall idea and/or program flow, to more and more specific, so you can quickly get a overall idea and then deep dive only in the thing you are looking for right now. It should only use acronyms that it have defined in comments at the top of the file (If that is too much work... then do not use acronyms) If the code can only be understood with knowledge from outside the codebase, then that must be documented in a MD file. Nothing fancy, just write the thing down. If you cannot explain it in text, then make a diagram (I recomend draw.io). Easy, quick, no the specific style does not matter, just make it easy to read.

there's just a lot of "if everyone adopts my particularly tortured way of coding, everything will be great" going on, when 90% of the time this is extremely stilted and adds instead of reduces complexity. and you just don't have to do that. you can code normal style and nothing bad will happen

You can write object oriented in C, functional in Java. Mono-paradime is bad.

The real world is complex, and picking 1 solution to everything means picking a bad solution.

Right tool for the right job.

"So you know how C is procedural, Haskell is functional, and Java is object-oriented? You may ask: 'what about Python?'

Well, Python is bullshit-oriented."

My friend, teaching me Python.

I hope it all works out for you!

I hope you find answers to all your trouble and your workflow gets smoother!

I hope you find cheatsheets to help you and manage to write notes that helps you remember!

bitch java is so fucking annoying why does the S in String need to be capitalized but the i in int has to be in lowercase??? why do you need to import a whole ass module just to take an input from the user??? why are all the commands so fucking long and hard to remember??? JUST DIE