Sunset programming? - page 6
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
You can use the cursor to control the internal memory in the EA by changing the context of its behaviour using the buttons.
For example:
1. Press button A and move the cursor to the right - increase the size of the array, to the left - decrease it.
2. press button B and left mouse button - new resource is created. At the same time, place a square on the chart.
3. Click C and move from square 1 (first resource) to square 2 (second resource) the data saved in it.
4. Press button D and move the cursor between the two objects - bind their parameters (which ones depend on the additional buttons).
And so on...
Here - the beginning of the revolution and transition to visual programming.))
In general, a cursor is a versatile tool. You can do almost anything with it, WITHOUT CONTROL ELEMENTS, if you switch the context of its values:
1. Change the value within a range.
2. Change the range boundary value.
3. Draw shapes.
4. Present the drawn shapes in the context of the process.
5. To represent a process in the context of a form.
6. Relate object parameters.
7. Manage internal memory.
8. Assemble new objects - templates and instances.
9. Destroy objects.
10. To change the location of objects in the kernel.
And many, many more things.
And all this without any ready-made windows, elements or studios. Just a cursor and buttons interpreting its values in different contexts.
Add to that the fact that instead of a keyboard, you can use interactive gloves and glasses that register the direction of your gaze to change the context. And you get the programming of the future.))
In essence, it all comes down to determining the focus of a person's gaze on an object and capturing the context of their actions by the controlling system.
What others are there?
probably at least - design, debugging, testing.
probably at least - designing, debugging, testing.
It turns out that before, when a programmer (or developer) was a programmer rather than a developer, he/she only programmed, but did not design and certainly did not debug or test.
It turns out that before, when a programmer (or developer) was a programmer rather than a developer, he only programmed, but did not design and certainly did not debug or test.
Debug a punch card or a microcontroller. A programmer in its original form is a coder. A developer is something else entirely. This thread imho discusses the decline of coders, implying developers without understanding what a developer really is in today's world.
Debug a punch card or microcontroller. A programmer in its original form is a coder. A developer is something else entirely. This thread imho discusses the decline of coders, implying developers, without understanding what a developer really is in today's world.
You mean that a program punched out on a punch card immediately represented absolute truth and never even had any errors?
A microcontroller is the same. Microcontroller programs were written immediately and without any errors, and without thinking about them beforehand, and without testing them afterwards?
This is the beginning of the revolution and the transition to visual programming.)
It has already been implemented about 30 years ago. You describe a highly specialised task and extrapolate it to the whole class of development tasks. Visual development has existed for a long time, both partially and fully automated. This in no way negates the necessity of developing other classes of tasks or even tasks solved by visual environments, to which greater performance requirements are applied, for example. Because any universalism sooner or later turns into a monster.
So, the programme punched out on the punch card immediately represented the absolute truth and never even had any errors?
A microcontroller is the same. Microcontroller programs were written immediately and without any errors, and without thinking about them beforehand, and without testing them afterwards?
What are you arguing with me now? That the programmer gradually became a developer, with an increase in the number of tools and task requirements?
I did not deny that.
Mining... Development of mineral deposits. Development of oil, gas, coal, ore deposits...
I wonder if designers have been renamed developers as well? Architects?