>game has impossible learning curve
Game has impossible learning curve
The trick is to use everything to make the code as easy to handle as possible instead of using retarded stupid monkey tricks.
Also use STD::Vector, its fucking good.
Why do you think people are paid 6 figures to code, retard?
>Mentally ill person makes the same thread over and over
I feel like all coding has a huge learning curve. The languages themselves are simple to understand with basic concepts but so much of modern coding requires external code to be integrated that you basically need to know several coding languages just to be able to write code in one language. Its pretty aids
dabs
This is only second time I made it!
>game has low skill floor but very high skill ceiling
>game is ugly at high level play
>game has a million mechanics, most of which are shit and more are added in every patch
My point still stands even if python is easy to learn. You still need external shit most of the time
>implying most programmers arent just stealing from the library and creating jank solutions on top of existing code
>Tutorials are way too long and it doesn't get fun until late-game.
where the fuck do i start with c++
And what's wrong with that?
>Game is tied to a shitty installer that causes problems with your system unless you put it on a VM.
>"dude, trust me, it gets good after 1000 hours"
Even the external shit is easy to use.
It's easy to install lots of libs like requests, bs4, flask, matplotlib, etc.
>I don't know how to code so no one else must know how to either
literally from the horse mouth
ie the dude that created it
>windows
hello world
fizzbuzz
simple calculator, advanced like sin/cos functions
ping pong game if you wanna learn graphics library
print text to file and read
what do you wanna do?
It's rare for the language creator to also be the most effective pedagogue.
>starting with the sequel
this isn't even a bad practice, as a programmer I definitely want to understand low-level shit but if I'm trying to get a product out the door I'd rather have an army of programmers that can stitch together something functional from proven libraries than a handful of expensive experts
>My game console can run almost all of the good games at almost the same quality. Exclusives aren't even fun anyway.
If I'm searching graph in C++ should I use iteration or recursion?
In JS I've found recursion to be faster than explicit stack.
If you say so, man. I think you've just become so accustomed to it you don't realize how jank it feels
iteration is the only way to guarantee safety, recursion is a neat trick for CS studies but can be impractical depending on how deep you're going.
In some languages you can catch the stack overflow (and they may have tail call optimization).
>implying you don't need to know how to program to do this
>implying you wouldnt do it if you could
>pip install
>import ____
so principles and practice using c++?
i want to learn from scrath
i know jackshit about coding, and with vidya boring me i have enough free time to dedicate myself to something
also i'm starting uni this year and i want to be ready for it(i'm not american so this won't put me in a lifelong debt and it won't be a waste of time)
That's a complicated question, and the answer is going to depend on your implementation and compiler, so just try and measure. Ultimately it is probably going to come down to memory coherency, how you lay out and access your variables in address space. One advantage to the recursion approach is it potentially allows the compiler to reason about what your code is trying to do a little better because the relationships between variables is more explicit, and use those stronger assumptions to generate simpler code. That doesn't mean you couldn't do better yourself if you iterate carefully.
LoL/Dota 2
Learning a language is like 5% max of the actual challenge of coding something. Knowing C++, C#, Java, JS, PHP, C, Lisp and some VB, I picked up Delphi in an afternoon.
Learning to properly use various libraries and advanced features is maybe 15-20%.
Learning how to build it can range from 1% to like 20% depending on the language and IDE. C# with VS you just press F5 but a decently compex C program will require you to learn makefiles, which are basically their own language.
Figuring out a working solution is maybe 30%, but making it scalable, efficient and maitainable is easily 60% of it
Making it stable and handling errors properly is another 15-20%.
You could just become a Pythonchad today but I guess you LIKE your virginity.
You don't just pick up a language in an afternoon.
Unless you mean I know basic syntax and constructs but actually knowing a language means knowing more advanced language features, how they are combined, what are things people generally avoid (and why) etc.
C++ has a huge feature set to try and learn.
Not really, because advanced features are entirely optional. You can write high performance production-quality C++ code that contains only function calls and basic math operators if you want. There might be more of that code since you are not taking nice modern shortcuts, but it is perfectly valid.
Delphi is basically C# without brackets desu. Both were designed by the same guy, with the same goals. With the IDE I never had to stop and wonder how to do something since it was so similar.
Like if you know Java, you can pretty much be coding in C# within a day and could do any basic CRUD application just fine but like I said, more advanced stuff, for example asynchronous programming, will need it's own learning time.
Its more like learning your first couple languages is most of the work. Then from those reference points you can easily pick up more, because all languages are fundamentally equivalent under the hood.
At least within the same category of imperative vs lambda calculus, but you don't have to ever learn lambda calculus based languages in order to be a successful software engineer. That stuff is more for the actual computer scientists.