Code Tree

[fluffy]

Everything basically in code comes down to a tree.

Lisp was the earliest laungauge to have a function syntax. (L stands for list)

Here is a simple example of functions.

F1(x):
x = x^2
Return x

F2(x):
x = x *2
Return x

F3(y):
x = 3
y = F1(x) + F2(x)
Return y

The pseudo code above is closest to python.

The problem I had for a long time is that I think in algorithms but I don't understand the syntaxes of specific programming languages.

I could not make data structures in Python because you have to set up long arrays weird.

I cannot use most functions and have to create my own.

Even then I have trouble.

A tree is simple but it's hard to make in higher level code.

I did not know how to put my ideas then into the computer.

All code is representative as a hierarchical tree graph and recursions.

At one point I wanted to do computer science but I didn't understand functions in Java.

There are no books that explain how to get Fortran onto a computer I could find earlier in my life because that's closer to Python.

BASIC looked interesting but it was too much like HTML to get any real work done.

Assembly I haven't looked at yet but it's closer to the machine code.

I never did calculus classes in school.
This may have influenced my thinking style.

File systems I had no use for until I found mostly that's what operating systems do.

Graphics I think work in ways I can hardly begin to imagine how the stacks come together.

Getting any kind of application on the desktop is really hard. I realized C++ corruption happens so did not explore it.

My view now is that I have to get some kind of work station with good tools. Open source never worked well for me. And buy real books not found at the library.

 

[Puffy]

There are plenty of free courses online for learning a programming language too? Have you also tried learning with other people who are learning programming so you can discuss concepts you find challenging and get direct feedback?

I learned through a combination of online courses, competitive coding websites, textbooks, boot camp with peers, and building shit and learning what I needed to make it work: stuff like simple puzzles/videogames. I found the boot camp helpful in that it provided me a structure of things I needed to learn/practice and a curriculum of resources to study rather than try and work out a curriculum on my own.

I’d also say, this is just me but I’d likely become confused trying to cover the breadth of languages you’ve been looking at too as the syntax is different in each. I think there’s something to be said for picking a language and sticking to it, particularly one that might get you a job, as you learn a language through practicing it every day.

 

[dr froyd]

most imperative languages (C++, java, javascript, python, Go, rust, etc etc) are just variations of C with slight differences in in syntax and utilities. At the end of the day it's all just
- declaration of variables
- functions
- loops and if-else

the point where one deviates from that is when going into things like functional languages (haskell, lisp) or logic languages (prolog). These require a radically different way of thinking

 

[fluffy]

I decided to write a book.

I have 6 pages done on the introduction.

I found 5 at the library that really are helpful.

Recursion explained by the head of the python foundation.

And two history books on computer culture.

I am going to look for people to help me irl

It's that my sister may know people is where I need to be looking as she's practically the only outside social network connection I have, she knows people.