Programming theory.

[Brett Nortj]

This thread is all about programming theory. Previously, I have forged new techniques in circuitry and programming alike, but this thread is dedicated to the software, as there is an engineering section for the hardware.

So, what is programming? Programming is where you type characters onto a text file and compile it to execute [operations] for you. This is a program, which you write. If you want to make a calculator, for example, you would write in, to start the program in a shell, as if it were independent of the computer's operating system, and, execute the running details of the program. This would allow you to interface with the program or run the video or sound file, or, execute another operation for the computer, maybe to write to [b.i.o.s.] that the compact disc player should be ejected or brought in, and, that it tells the hardware what to do, although this is hardware related, of course.

So, let's begin with some theory that will help you understand what [robots] do? I love robots, and, they are for operations where the individual execution is activated or calculated - yes you could ignore the rest of the manual telling you how to program and just use robots and things that move between them and their operations, they are that good!

Now, if you were to observe that robots would be inside a shell, or, be where the program begins the robot, they are like little programs inside the program, okay? This means they will bring calculations and operations to the fore that converge into one 'action.' Remember, the fundamental of programming is, "If this then this." So, you want to make robot that link between other robots, that would be a simple robot written right at the beginning of your text file, in a different colour, where you can number them and figure out the order, where you could put them into order, and, sequences, all in one neat little text entry.

With programming, you need to tell the circuits what to do. This is like turning a light bulb on or off, the circuit will simply conduct energy to the next circuit on the bus, and, then they will affect the changes you are making. This is done by writing the code into the text file and having it send it to the circuit board as if it were a tiny charge, if you know anything about 'electricity.'

So, to write a program you need to simply instruct the text to carry that charge to the circuit board via translating bytes of text, which it just reads, as it is a text file converted to a 'charge file' through each character representing 'the chime of the piano,' okay? This would mean the computer just plays your stuff!

Now, to program into the computer, you need only write to a the text file to activate these changes. This would mean the text will be like a program in itself, and, this text you must keep on saved file, to make sure you can change it, yes? Or you will be faced with a lot of decompiling to make changes. If you want to test something, write the files individually, and copy and paste the them together to test more instructions. This is the least stressful and most steady way to learn to program basics, and, then you will be able to piece together bigger files, and, then you will be able to keep the original for patches, where you override the program with another file that you write, of course.

[Sensei]

Congratulation to show that you have no idea what you are talking about.

You don't even know proper terminology which is widely used even by non-professional programmers.

1) procedures, routines, sub-routines, functions. If inside of OOP class, they're called methods.

https://en.wikipedia.org/wiki/Subroutine

2) conditional branches, or unconditional branches.

https://en.wikipedia.org/wiki/Branch_(computer_science)

3) control flow of program

https://en.wikipedia.org/wiki/Control_flow

4) source code.

https://en.wikipedia.org/wiki/Source_code

5) compilation and compiler, interpretation and interpreter.

https://en.wikipedia.org/wiki/Compiler

https://en.wikipedia.org/wiki/Interpreter_(computing)

 

[Hitulseo]

Programming theory encompasses a wide range of concepts and principles that form the foundation of software development. It includes various topics such as:

Algorithms: The study of step-by-step procedures or instructions for solving problems or performing tasks.

Data Structures: The organization and management of data in a computer's memory, including arrays, lists, stacks, queues, trees, graphs, and more.

Object-Oriented Programming (OOP): A programming paradigm that structures code around objects, which encapsulate data and behavior.

Functional Programming: A programming paradigm that focuses on writing code using pure functions and immutable data.

Design Patterns: Reusable solutions to common software design problems, providing templates for structuring and organizing code.

Software Development Life Cycle (SDLC): The process of planning, designing, developing, testing, and maintaining software.

Software Architecture: The high-level structure and organization of software systems, including the choice of frameworks, libraries, and patterns.

Testing and Debugging: Techniques for verifying the correctness and quality of software, as well as identifying and fixing defects or errors.

Optimization and Performance: Strategies for improving the efficiency and speed of software, such as algorithmic optimizations and code profiling.

Code Modularity and Reusability: Designing code that is modular, modular, reusable, and maintainable for easier development and maintenance.

These are just a few examples of the broad range of topics within programming theory. Each topic contributes to understanding the fundamental principles and best practices in software development.