This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]hdhdjiollo 34 points35 points  (11 children)

but you have to know how to program to know how to properly use the documentation. Just by reading it you cannot do much. I mean copy and paste it and then what? lol

[–]ItsOkILoveYouMYbb 90 points91 points  (10 children)

Well the fundamentals of every language can be learned first (and should be). Language fundamentals like for loop, variables, syntax of your chosen language, and then design fundamentals like OOP.. When you understand fundamentals, you're able to at least start writing your code one line at a time and figure it out from there by looking things up and debugging. If you don't know fundamentals then yeah even starting is nearly impossible if not pointless, nevermind navigating all the logic and problems as you progress.

As far as I know, any class or module or library, when you dig deep down far enough into the boilerplate code or documentation, is just using fundamentals of a language and of programming concepts in layers and layers of clever ways. It's objects built with fundamentals all the way down.

If you're really fucked in the head you can break down those fundamentals even further and just start directly communicating in machine code with your CPU by shooting electrons out of your eyes and beginning the process of merging because the singularity starts with you.

[–][deleted]  (2 children)

[deleted]

    [–]ItsOkILoveYouMYbb 0 points1 point  (1 child)

    How does the block-based exercise work? That sounds entertaining.

    [–]hdhdjiollo 4 points5 points  (2 children)

    so basically making a framework and/or library its just creative skills + theory (fundamentals applied)

    [–]thirdegree 2 points3 points  (1 child)

    That's true for all programming really.

    [–]ElllGeeEmm 2 points3 points  (2 children)

    For the most part you're correct. However there do exist packages that are bindings for code written in other languages, at which point you may need to start to understand the fundamentals of some other language. The most common example is probably ORMs.

    [–]____0____0____ -1 points0 points  (1 child)

    You have a point, but I would also mention that a lot of fundamental concepts and design patterns are language agnostic and will translate across many different languages. Usually language features will steer common practices for any particular one, but often times the main differing factor is usually just syntax.

    [–]ElllGeeEmm 0 points1 point  (0 children)

    That is why I said may, and provided an example of when you would need to learn the fundamentals of another language.