Subject-Oriented Programming Universal Software Model -- the Future in Software! 100 programming languages? Why not only one? I built it (60% ready) as a programming language, but it can be viewed as an Operating System for managing any informational problem. th-cam.com/video/FbqEi_i1Fro/w-d-xo.html The entire system is based on only 3 main concepts: 1. Parameters of the problems. 2. Subjects (static and dynamic) as special lists of parameters. 3. Informational Individuals as a Matrix of Types of parameters and subjects. The Matrix of Types is a unique, universal system for representing parameters of the problem on three levels of complexity (Independent parameters, Static Subjects and Dynamic Subjects) and three context of work (H, M, K). The entire management procedure is a part of the usm language. The user (analyst) is deciding the details about parameters, such as type, short name, a description (optional for independent parameters), and the place into the matrix of types. In addition, a subject can be viewed as an informational cell, and an Informational Individual is becoming a chain of informational cells (software DNA). There are here two big changes of paradigms in software world: a. From a very, very complicated Object-Oriented Programming (OOP) to a simple and natural Subject-Oriented Programming! b. From the Main() function to the Brain() function! Any Informational Individual is starting with the Brain() function. Too much human effort is stuck on the current software model. More real problems are waiting to be solved. You would be interested in Subject-Oriented Programming Fundamentals (Parameters, Subjects and Informational Individuals). The Informational Reality is about Parameters and Subjects, much more than software abstractions, objects, or classifications. More simple is not possible!
Since my start of journey (goes back to 2015) as a self taught developer, you are one of the instructors I have been following since then. It is always so nice to see you spreading knowledge. Thank you Sir
Thanks, really keep up with these kinds of videos, i'm currently taking your typescript course and this makes me feel that there's a long way to go to achieve such a level as a developer but also such journey can be super rewarding!
It's not how many you should learn. For educational purposes, it's good to learn at least some interpreted, something managed, and something very close to machine level. Gives you a better understanding of what makes a process tick.
Thank you for these amazing videos max, your courses on react, angular and flutter has helped me lot. If possible need more sections in go course with new features.
Sometimes learning a few languages in certain fields could increase the chance to get unique position. Python and javascript fit good for fullstack position (Lets say React + Django). It's depends on what your goal in the end of the day.
You said you began by learning C as your first programming language. Does it really matter what programming language you begin with? I ask because if you want to become a web developer naturally you start off with JavaScript for the frontend. But by starting off with JavaScript can that turn you into a bad programmer? It seems JavaScript doesn't follow the natural conventions of programming like C, Java, C# to name a few. Am I correct in my thought?
I don't think it's about programming languages. It's about knowing basic concepts in software development/programming. Programming languages are just a tool. However, I think that you should have an overview in order to be able to choose the right tool for the problem to be solved.
Unless you wanna do something that only a specific language can do, how many languages you need to know is just one. But, make sure you know it well.
I only know brogramming languages.
I like how you quoted: "I started with C as it's the perfect first language, why not ? ... little pause.. maybe not :D "
Great, when can we expect a rust course then?
Subject-Oriented Programming
Universal Software Model -- the Future in Software!
100 programming languages? Why not only one?
I built it (60% ready) as a programming language, but it can be viewed as an Operating System for managing any informational problem.
th-cam.com/video/FbqEi_i1Fro/w-d-xo.html
The entire system is based on only 3 main concepts:
1. Parameters of the problems.
2. Subjects (static and dynamic) as special lists of parameters.
3. Informational Individuals as a Matrix of Types of parameters and subjects.
The Matrix of Types is a unique, universal system for representing parameters of the problem on three levels of complexity (Independent parameters, Static Subjects and Dynamic Subjects) and three context of work (H, M, K). The entire management procedure is a part of the usm language. The user (analyst) is deciding the details about parameters, such as type, short name, a description (optional for independent parameters), and the place into the matrix of types.
In addition, a subject can be viewed as an informational cell, and an Informational Individual is becoming a chain of informational cells (software DNA).
There are here two big changes of paradigms in software world:
a. From a very, very complicated Object-Oriented Programming (OOP) to a simple and natural Subject-Oriented Programming!
b. From the Main() function to the Brain() function! Any Informational Individual is starting with the Brain() function.
Too much human effort is stuck on the current software model. More real problems are waiting to be solved. You would be interested in Subject-Oriented Programming Fundamentals (Parameters, Subjects and Informational Individuals).
The Informational Reality is about Parameters and Subjects, much more than software abstractions, objects, or classifications.
More simple is not possible!
Since my start of journey (goes back to 2015) as a self taught developer, you are one of the instructors I have been following since then. It is always so nice to see you spreading knowledge. Thank you Sir
Thanks, really keep up with these kinds of videos, i'm currently taking your typescript course and this makes me feel that there's a long way to go to achieve such a level as a developer but also such journey can be super rewarding!
It's not how many you should learn. For educational purposes, it's good to learn at least some interpreted, something managed, and something very close to machine level. Gives you a better understanding of what makes a process tick.
Thank you for these amazing videos max, your courses on react, angular and flutter has helped me lot.
If possible need more sections in go course with new features.
Sometimes learning a few languages in certain fields could increase the chance to get unique position.
Python and javascript fit good for fullstack position (Lets say React + Django).
It's depends on what your goal in the end of the day.
Haskell, Elixir, Clojure are cool
Your go course is pretty cool mate!
-First Step: start learning C ✍️✍️👌 got it
Greetings Max, Max here ;-) Guess you just subscribed to working on a Rust course? Or already in the pipeline? ;-)
Gruesse in die Heimat!
Rust course when????
How many have you forgotten?
Thanks for the info Max..
Great Job Max. Thanks 😎
Can one language always be translated with high fidelity to another by formal program transformation?
You said you began by learning C as your first programming language. Does it really matter what programming language you begin with? I ask because if you want to become a web developer naturally you start off with JavaScript for the frontend. But by starting off with JavaScript can that turn you into a bad programmer? It seems JavaScript doesn't follow the natural conventions of programming like C, Java, C# to name a few. Am I correct in my thought?
Can you consider doing. Net video with newest version of c#.?
Waiting for your tutorial on Udemy about Android development with Kotlin and Jetpack Compose.
kindly make swift and devops course
I don't think it's about programming languages. It's about knowing basic concepts in software development/programming. Programming languages are just a tool.
However, I think that you should have an overview in order to be able to choose the right tool for the problem to be solved.
Valuable content as always!
How is it valuable?