Advertisement
SpellsOfTruth

Learning2Code

Feb 25th, 2020
163
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.15 KB | None | 0 0
  1. -1st link https://docs.python.org/3/reference/index.html
  2.  
  3. -2nd link https://www.softcover.io/read/e4cd0fd9/conversational-python/ch1_basicio_types
  4.  
  5. -3rd link https://spellsoftruth.blog/2020/01/03/divinely-simple-computer-programming-part-1-the-buzzword-environment/
  6.  
  7. -4th link https://templeos.org/
  8.  
  9. from this comment: "If your an absolute beginner. Learn python. Its built so humans can read it, not so machines can read it. This makes things much easier to understand. Most people start with tutorials and use the primary source as a reference, flip it, start with the primary source and use the tutorials as a reference. Dont read tutorials first read the primary source first then use the tutorials to explain things you do not understand in the primary source, then continue reading the primary source. Start from chapter 1 read to chapter 10. When you get to a word that you don't understand. Look it up in the tutorial and understand it before continuing. The most important words in computer programming are environment, context, name-value pairs(symbol tables), invocation/invoke, syntax, parser, operators, precedence, statements, and expressions. An environment is the container of code, there are many differently sized containers with many different terms for them, here are some common ones you are sure to encounter: application, project, package, module, file, namespace, object, class, interface, struct, method, function and other similar terms (sorted largest to smallest, relatively). All of them are simply different sized environments. This is done because the closer the code is physically, the faster the computer can process it(not as relevant today, its more done for organization reasons and so names don't overlap). Context is which of the layer-like environments is currently running. Kinda like how in English words can mean different things in different context. Its important to understand what execution context you are in because names(words) can mean something different depending on the context (like words in english). The rest I explain in my link in the following pastebin. The 1st link is the primary source. 2nd link is good beginners tutorial on python(use the tutorial as the reference and the reference as the tutorial). 3rd link is a link to one of my articles explaining the rest of those examples. If you want to get really crazy, learn the ins and outs of the operating system TempleOS. Its an entire fully functioning operating system under 100k lines of code(the program im using in my video is TempleOS). TempleOS lets you mess with things normal operating systems have purposely blocked or hidden (for security). Windows is like 50-60 million lines of code, linux is like 25-40 million lines of code. Mac is 40-50 million. Very few people know exactly how everything in those operating systems work, and it took them a lifetime to learn it. TempleOS has all the basic parts, has no file permissions, no memory protection. Meaning you can fuck around in the kernal, touching hardware ports, you can change the kernal (completely unique kernel, windows is dos and nt kernel, mac and linux are unix kernels, TempleOS is its own unique kernel thats only like 40k lines of code). Fuck around in TempleOS for a couple years, you'll be better at programming than 25 year professionals because most professionals have no idea how the operating systems work on a kernal level so they dont have as deep an understanding of what is happening in reality. TempleOS uses 1 language, its a mixture of around 75% C and 25% python. I use it in my videos because using it makes me remember that programming can be fun and not just droll and monotonous. Its a very steep learning curve but its pretty well documented inside the code, just hit f1. You'll need a basic understanding of C programming language(pointers, malloc, etc) cause it doesn't explain those concepts. It forces the programmer to think for himself again, instead of rely on google and stack overflow when problems occur. You will crash it many many times, but thats cool cause it boots in 1 microsecond. If you break it, restart and be back to coding again in 1 microsecond. Save often. Here the pastebin, TempleOS is 4th link."
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement