Regardless of the profession we have chosen, we all have gained experiences in our field of work that have paved the way for our progress.
I do not have any other profession or field, but what I can talk about is my field, which is computers and programming. When we want to write a program for a system, we must first be familiar with it. We must know what facilities we have and what limitations we have in facing the desired system. For which platform do you want to develop the program? Are you dealing with mobile phones or personal computers? What are your requirements and limitations? Of course, when you want to write a program for a microcontroller, you must write an optimal program. In fact, you may have memory limitations and also need speed in execution.
In programming, we have principles that we must follow when creating a program. The principles, or in fact, the ideal or optimal program or whatever you call it, are based on execution speed and memory size, readability, maintainability, security, scalability, testability.
Of course, sometimes having all these things at once is difficult or at least a little difficult, but this is the ideal and it is definitely not necessary to achieve them all at once. The important thing is to write a program that takes these principles into account as much as possible. In fact, by observing the principles of software design, we will bring our programs closer to the ideal, even if it is not a pure ideal. In this regard, in the programming dimension, we spend time designing programming algorithms, the goal of which is to create optimal and ideal programs.
You may tell me that computers have advanced today and we do not have a problem with the amount of memory. That is true, but this does not mean that you can write programs however you want and occupy as much memory as you want. So what do the rest of the programs in the system do?
I may need to write posts about designing algorithms to understand what I mean, but what you should keep in mind is that the programs you design must be optimal. As a programmer, you are obligated to design an optimal program. We use software engineering principles to create our software, but that doesn't mean that software engineering principles can be flexible and creative if they are applied with the right understanding and in line with the needs.
In fact, I believe that we should use an optimal software design approach depending on our needs, which of course is flexible and is designed and implemented depending on the environmental factors involved in the production and development of the software.
When designing any software, you have factors that are involved in the production of the software and definitely need to be managed.
The personnel involved in the project, the amount of design and production time, the amount of budget available, etc. must be managed. Each factor involved in software development also has its own internal factors.
If we look more internally, we see that there are many cases and factors involved in the project in the design and production of software. Almost what we do today in the production of a software is the use of programming teams, where perhaps each team or at least each of our personnel works on different parts of the software. Being able to manage teams or personnel, being able to manage errors, and being able to create an environment where the final program can be well adapted by putting different parts together and forming the final software is a challenge ahead. This is where I believe we need to have a software development approach.
I personally started many programs during my programming experiences that never reached the end! Do you know why? Because I did not follow the principles of software design. I started designing without a goal, without any plan, without any approach and went ahead. I wrote the parts I needed and when I got stuck in a pile of code, I could not figure out what I had done.
This is what you are in a programming nightmare. Unorganized and messy code that does not know how to be used. If we are very lucky, it compiles without errors, but the real nightmare begins when logical errors are seen in the program. You might call them a bug! I don't know what you call them, but when a program has no errors but doesn't work properly somewhere, there is actually a logical error in the program, and if you are lucky, maybe in this period of your life you can discover the reason in your busy and irregular code. But there is another solution, write a will so that your descendants can continue your path so that they can solve the logical error. Of course, this is a bitter joke, but by designing and following the principles of software design, you will definitely avoid such nightmares.
The post I wrote is not just a simple note. You are in Hive today. A blockchain on a vast world and of course a crypto competing with other cryptos.
I see here code snippets that you easily skip over. Let me tell you simply. Here you see code snippets for voting, posting, commenting, etc. and even code snippets for sending tokens and internal trading in Hive. You easily skip over them. You may think of them as simple codes, but if you put all these small codes together in a programming idea, these ecency and peakd frameworks are formed. Yes, that's right. How you use these simple codes is important. These simple and inefficient pieces of code, when put together with a specific and planned approach, form beautiful ideas.
Anyway, take this from me: Don't ignore any code.
