Personal Technology Development-demand-oriented

I have seen many cuer plans to give up it and engage in other industries. Here I respect personal choices and wish them a good development.
However, some opinions are obviously incorrect and unreasonable, that is, after the age of 30, technology will abandon you and the company will abandon you. Here I will explain it in two ways.
I personally feel that there are two layers of technical knowledge: one is for technology itself, and the other is for demand.
Just graduated students are basically at the technology level. From the discussion of C # Learning Java, we should know that they are pursuing technology, not any software requirements. So we need to develop an application software, using C # programming or Java programming? Of course, all of them can be done, and most of the time it depends on the customer's choice. For junior technical positions, their job requirements mark exactly what development language and development platform you use. Therefore, many of them have written tests before the interview. After all, the primary job is based on the design requirements, one-on-one development in the original architecture.
So let's take a look at the middle and senior technical talents and positions, which are generally considered in which direction, the positions require similar experience in a certain project to be preferred, good at team communication, etc, basically, you will use a pure interview method (a few companies may still have a written examination, known as the company culture, without making more comments). After the interview, you will learn what you have done in the project, what problems have you encountered, how to meet the requirements, how to cope with the changes in customer requirements or unreasonable requirements of the customer, or your understanding of the software field, there is room for improvement and optimization.
In fact, from the perspective of comparison, after entering the intermediate and intermediate stages, the technology itself is only the foundation, and the purpose of the technology is to focus on the needs. Just as you can see shell scripts written by foreigners to schedule and manage database jobs, their scripts are very concise. Like Regular Languages, awk and SED's advanced usage cannot be found at all, so what do you say they are behind in technology? In fact, it is not because they are demand-oriented. As long as they fully meet the system logic we designed and can meet system efficiency, is it so important for advanced usage? In addition, the common usage is the need of software management, because every block has annotations, so that everyone can understand it and the continuity of software is strong.
Let me talk about how enterprise application software systems feel (mainly in the bidw field). There are dozens of products and five database products in mainstream data warehouses, the product version has been upgraded almost every two years. With new features, the database itself is also evolving. Even database products dedicated to data warehouses are available, and programming languages are also varied. If you want to face technology all the time, you will be chased by technology for the rest of your life. You may not be able to get familiar with a new product that has just graduated for two years.
After the age of 30, I was eliminated? First, let's take a look at what customers need in the bidw industry. These products, programming languages, and databases are in this direction. What enterprises want is to build a data warehouse to achieve Bi and data integration step by step. What is Bi implementation? Why data integration? The first is for enterprise-level data analysis and mining, and the second is to facilitate innovation in other systems, such as enterprise planning systems, data source self-data warehouses, at the same time, it also puts the results back to the data warehouse for comparative and comprehensive analysis. It can also form a unified enterprise data perspective in a multi-system data warehouse, and can track the changes of important business of the enterprise in real time.
After learning about this layer, I was wondering what the various functions of these products are. Why do we need to upgrade the products and what other functions? Through constant thinking, I can start development on my own, and concentrate on planning, design, and management, so that others can implement it. Maybe I am not proficient in new product functions, but is it important? I only need to know what development effects I want and what tools can do. If the tool doesn't work or I am not familiar with it, I can replace it with a stored procedure or shell.
Data Modeling Technology is also designed to meet customer needs. The dimensional model breaks through the traditional third-paradigm modeling idea. When we query and analyze enterprise data, we find that too many large tables are associated with each other, resulting in low efficiency, as a result, the modeling technology was designed to address this requirement with a considerable degree of redundancy. The modeling technology oriented to things features and behaviors used space for time. I think if there were not so complex report requirements at the beginning, this modeling idea does not appear.
The purpose of data aggregation is to reduce repeated data computing and store the computing results directly in the database so that end users can query the data more quickly. At the beginning of development, this method worked very well, but people later found that the summarized data could not be returned to the original atomic data. If the demand changes, the summary rules also need to change, people need to think of multi-layer modeling. Until now, the data layers of some big projects in the top 500 enterprises have reached about 10 layers. The development of these application technologies is also demand-driven.
Through my introduction, do you think that after the age of 30, they will be either eliminated by technology or eliminated by the company?