I just tweeted below to understand and use “No Code“!
From yesterday, I explained about “no code” so that it is easy to understand the contents learned by Professor Kojini, a beginner in programming.
I started learning “no-code” a few months ago, but the first comment I finally met was Manablog’s Manablog explaining “no-code” on YouTube. I immediately learned this video as a “digital textbook”.
While digging into the contents for myself, I am arranging it so that even beginners can understand it easily.
table of contents
1) Introduction
2) What is no code?
3) 5 non-coded standard tools
4) Difference between no code and low code
Yesterday, I mainly explained the content of Mr. Manabu about 1) and 2).
In today’s part 2), I will explain what I learned from articles other than Manabu.
Below is the content today.
2)-1. Programming ≠ writing code
-2. No code is new programming
-3. History of programming = History of abstraction
Today’s contents are very important for Mr. Kojini, who has always advocated the history of learning something new in order to learn something new.
I would appreciate it if you could read it. If you have time, I would be very happy if you also read “What is No Code? ①“.
If you read Kojini’s Cafe in the future, you will understand the following.
✅ Understand the basics of No Code
✅ Understand the future of programming
✅ Know how to earn with no code
Let’s get started!
◇
That’s why I thought other programmers would research how they think about no code. In fact, there were many suggestions, so to the extent of my understanding, I’ll show them below.
◇
I found an interesting phrase in “note” and read it immediately.
“I’m an engineer in 2030. I can’t write a code. (shinji)”
This is a guess for the future of “no code”!
Ten years from now, Manabu said, “No one understands it.” However, thinking freely and thinking, it would not be strange for such an opinion to come out.
For example, here’s an interesting “future-proof” article in my knowledge:
In New York City in the 1800s, there were 200,000 horses. I don’t get an image, but horses played the role of the current automobile. The biggest public health challenge in New York City at the time was treating horse manure. Each horse defecates 10 kg daily. Since the number of horses is 200,000, 2 million kilometers of horse dung, or 2,000 tons of horse dung, was scattered on the streets of New York in one day. In a sense, it is good to imagine the condition of the stables, cowsheds, and pigs, but you can only imagine the unpleasant “smell”.
A large amount of flies flock to horse droppings. It has become a route of infection for various diseases, and it seems that 20,000 New Yorkers lose their lives each year due to an infectious disease.
People who lived in this era imagined New York decades later.
“Isn’t the number of horses increasing and the roads become mountains of horse droppings?”
“Isn’t there anyone who lives here because of the smell of horse droppings?”
“Isn’t there a concern that the plague will spread and the population will decline?”
These answers don’t mean you’re really wrong… but actually.
If in the early 1900s and New Yorkers, “Within a decade, passenger cars will become widespread, horses will disappear from New York, the problem of horse droppings will disappear. The infectious disease from flies will disappear. Instead, people will be hit by cars and live. No one would have believed it. However, when Ford launched the Model T in 1908, the horses were quickly dragged off the protagonist of transportation and transportation. And the infectious disease disappeared, and traffic accidents became a new social problem instead.
The story has derailed (laughs), but it’s that difficult to predict.
Let’s go back to “no code”.
2)-1. Programming ≠ writing code
According to shinji, it’s “programming ≠ writing code”. This is easy to understand if you unravel the history of programming.
Early programming involved punching holes in cards called punch cards and loading them into a computer for processing.
According to wikipedia, “Programming is the process of designing and building an executable computer program for the purpose of obtaining a particular computing result.” Can be said to be changing.
If you think of it like this definition, the “no code” we are talking about today falls within this definition. Of course, it can be said that “No Code” is not the final chapter because it changes with the times.
For me, who always thinks that it is “history” in order to deepen my understanding of everything, it becomes a convincing definition.
2)-2. No code is new programming
In addition, Jeremy Ho wrote the following article.
“No code is new programming (Jeremy Ho; Uber Product Manager)”
All of today’s software is built on top of abstract layers to help developers work more efficiently, with each layer nicely hiding complexity. Software libraries abstract common logic, frameworks abstract common patterns, and APIs abstract the entire business domain. All programmers are already standing on the shoulders of giants.
No code is no different. It abstracts the code in software.
The “abstraction” here is to make it possible to handle complicated things easily.
According to Mr. shinji, “Generally, many programmers write some original code, but connect processes abstracted by the assets of the code built by the ancestors by open source etc. I’m building web services etc. I don’t write and implement all the processing myself.” This is of course convincing.
It means that we are now living while borrowing the wisdom of many predecessors. It also means that programming is like no other.
In this way, even in the current software development, it is said that it is partially implemented without code and stands on the shoulders of giants. No code is essentially programming, it just abstracts all the code.
Lastly, I mentioned earlier that “history” is important, so I will try to understand the history of programming.
2)-3. History of programming = History of abstraction
The most primitive programming language is called machine language, and it is the code written by combining 1 and 0 as shown in the figure below.
Machine language can directly operate all the functions of CPU, and there is a possibility that the program can be written most efficiently in terms of CPU performance.
It is a combination of 0 and 1, so it is hard to see and the eyes flicker. In this way, machine language is hard for us to read and hard to write.
In order to solve these disadvantages, an assembly language was created in which English words and symbols correspond one-to-one to machine language processing. The left side of the figure below is the assembly language.
Assembly language is converted to machine language by a converter called assembler and passed to the CPU. Machine languages and assembly languages like this are collectively called low-level languages.
The high-level languages we are familiar with, such as C programming language, PHP, Ruby, and Java, have made this more human-readable and readable.
From this perspective, it would be a natural advance to further abstract the high-level language and lead to no code.
I’ve talked about the history of programming language abstraction and the changes in input methods.
Considering that there is no code in the future of abstraction, it looks like the image below.
◇
Up to this point, I have explained “no code” and “programming”.
Thank you for reading to the end.
The information of Manabu, shinji, etc. + information that I independently researched was mixed and transmitted.
In terms of content, I will pick up what I understand is important.
I would be more happy if the information was useful to you.
This week, I would like to write about “programming” from this “no code”. Thank you.
See you again! Ciao☆彡
◇
Addendum: Ultimately, I hope to reach the point where I can create something with “no code”. I will try my best, so I would appreciate your support.