Would anyponer know where to start when it comes to having knowledge of discrete math and algorithms, etc. but being terrible at coding itself? Any good books? Looking into pic related.
Man I love coding
I'm kind of a rookie but the game's coming together.
Good to see some enthusiasm for it.
What's the game about, if I may ask?
Silly Pinkie Pie, you can't have a book on your head!
>>3636>Introduction to Algorithms is a good book to have as lookup for all kinds of algorithms. Is a great book to look up efficient way to do different operations from sort functions to tree functions to graph functions etc.>The C Programming language is a short book that will tell you all you need to know to code in C (it's the manual)
Sadly I am not sure what is a good book to get into coding itself will be. You might look at home pages for Computer Science courses in Universities and see what the curriculum books they use. I know a lot of them (or at least where I went) started with Java because it is a easy language to learn OOP in and structured coding, then moving on to C, and then the language you feel comfortable with.
But also think about what you want to code. If you want to make Windows apps C# might be a good way to go. If you want to code for Embedded Systems and Micro Controllers pure C might be good. If you want to make games C# or C++ or what language the graphic library uses might be the best language to focus on. If you want to make websites PHP, Dot Net Core or Node.js or any of the other languages and libraries for Web development is a good start.
Much can be learned from youtube videos and tutorials, reading the manuals for the language you want to write for, and also forum posts or sites like stackoverflow.
Basically imagine Sonic buttfucked Dante so hard the kid came out teleporting around at mach fuck with a Keyblade but better and less retarded also you've got a ghost fren and you're in a fucking coma
That's the game but described badly.
>>3642>>The C Programming language is a short book that will tell you all you need to know to code in C (it's the manual)
A splendid idea.>If you want to code for Embedded Systems and Micro Controllers pure C might be good.
I really like C, because it's about as low-level as you can get without directly tooling around with the bits in assembly.>If you want to make websites PHP, Dot Net Core or Node.js or any of the other languages and libraries for Web development is a good start.
Boo hiss! Node was the death of me. Maybe later down the line.>Much can be learned from youtube videos and tutorials, reading the manuals for the language you want to write for, and also forum posts or sites like stackoverflow.
Are there any general tips out there? I had to figure out myself to use the debugger; most kids didn't even know to use it in upper division classes(!).
Best way to learn programming is just to do it. make up a project that's sane for your level, then research how to do it, then do it. repeat until you've built knowledge.>>3646
C gives you complete power while being so simple. It's not just low level, it's effectively comfy assembly. Linus has described it as him being able to "see the assembly" when he looks at the code.
Almost 50 years old and still the best language around. (Pointers are also extremely fun)>Are there any general tips out there?
I could give a few. Any topics and how advanced are you?
Right now I'm learning OpenGL in order to make a game engine in C. It's fun.
been playing a lot of classic Doom lately, experiencing different mods and wads.
the Isabelle Companion Mod is brilliant! I wish there was a pony companion mod. What I wouldn't give to face the armies of hell with Twilight, Aryanne, or Rainbow Dash at my side.
>>3647>Pointers are also extremely fun
Playing with pointers in C and do typecasting of arrays or other objects to pointers is as you say truly fun and a zen like experience. I miss malloc and realloc and having full control of what happens instead of relying on the language to do the GC for you. I should find a project to do to get into C again for the simplicity and beauty of the language.>Right now I'm learning OpenGL in order to make a game engine in C. It's fun
I can recommend looking into the "Game Programming Gems" book serie, and also GameDev.net for info and nice tidbits.
>>3647>I could give a few.
Any would be appreciated.> Any topics
None in particular, really. Maybe if there are some in "The C Programming Language" book that's been mentioned above, or if you could point me in the direction of certain tools to use, like gdb.>and how advanced are you?
Not very. Would it be enough in giving an accurate idea to say that programming assignments took the most amount of time, for all the wrong reasons?>make up a project that's sane for your level, then research how to do it, then do it.
That doesn't sound too bad, when you put it that way.
Wouldn't this bread more easily found and logically placed at >>>/cyb/
That'd be a great question 28 months ago.
>>6918>28 months ago
Exactly. Because nopony is able to find it.
Did you just feel like necro bumping a thread on page 10 of a slow board on a slow site for fun, or did you have anything new to add?
>>6922>you have anything new to add?
It is already stated. Will this bread be kept at /ub/ or moved to /cyb/?
A yes or no will suffice.
Could have asked on /qa/ or something. Instead of asking what grave to put the thread in.
I see. The insurmountable bureaucracy.
Better start a new bread them.
>thread is out of people interested in the topic, is abandoned for two years
>boomer wants to be credited with resurrecting the thread but doesn't know anything about the topic
>bumps just for the attention, doesn't have any topical discussion or prompts, not even a shitty faceberg meme
>gets negative attention
>nipples harden at the prospect of claiming superiority
>cite "insurmountable bureaucracy" when told that bumping a dead thread just to ask mods to put dead thread on another board is fucking stupid
>threatens to make thread
Allow me to make a prediction:
>new thread is made, doesn't have anything to say or knowledge to share on the subject
>since nobody's interested in the topic anymore, bumps it continuously for a week with half-baked memes stolen off of /g/
>"WHY ISN'T ANYONE ELSE POSTING, DON'T YOU SEE I'M SAVING THE SITE???"
Namefagging>boomer wants to be credited with resurrecting the thread
An assumption without any backing>but doesn't know anything about the topic
Slander 101. You don't know that.>bumps just for the attention
You don't know who that anon is. Unless you are staff sneaking behind.>Allow me to make a prediction
You are just posturing out of spite.
Trust me, the way you type and post is a universal constant. You post ponies, but only as smug reaction pictures or specifically to posture about people not posting enough ponies. You use terms like slander, posture, projection, any time you want to redirect a topic. And you complain about the slightest inconvenience like asking on /qa/ instead of bumping a dead thread that's already on its way to the archive just to bitch about the probably-fucking-dead OP's choice of board two years ago.>An assumption without any backing
You do this shit all. The. Time.>You are just posturing out of spite.
Yes. Yes I am. Because I want you to die of a stroke. You leather-bound fossil.
>>6931>You post ponies, but only as smug reaction pictures or specifically to posture about people not posting enough ponies.
Ahem, Boom Boom here, some faggot was naming my name.
You don't want me to post screenshots showing my pony posts. Do you? And I am referring to NOT smug reactions, but pure 100% unadultered pony posting on pony threads.
Okay. In that case, I want two of you to die of strokes. Thanks for your input.
>>6931>You post ponies, but only as smug reaction pictures
I'm suspecting this is derived from a deep envy to my unparalleled pony meme ammo and the speed I deliver them in full auto mode.
Though you are correct, you did not use /qa/ or report the thread to do this. >>6918
is correct and you are a menace to this damn site. Looks like you need another reminder to fucking use the proper channels.