Value of the business model (another way for programmers)

ArticleDirectory

• 1: How to balance Business and Technology
• 2: How programmers learn business
• 3: extract business models based on business and technology

Recently, I have been busy with the construction of basic databases of new companies and the development of some business systems. I have come into contact with some more thoughtful technical personnel who have found many important things to think about, I also learned some valuable experiences. I would like to discuss them with colleagues here;[Wang qingpei has all rights reserved. For more information, please sign it.]

It is said that technical personnel should pay attention to business learning and training. Only after they are proficient in the business can they give full play to the technology. In fact, I do not agree with this sentence. Why? From my personal experience and experience, this is correct. Of course there is no such thing as standing on usProgramFrom the perspective of staff, I absolutely recommend that technical staff always focus on technology-based business. Some friends may be on the verge of fire. The technical assistance service should be bigger than the technology, and everything is relative. If you focus on your business, you can send your personal fortune to the company. If you focus on technology, you can keep your personal fortune. Those who have experienced this sentence will understand it, and I will not explain it.

1: How to balance Business and Technology

I think we all know about the Chinese market. For average enterprises, technology is not important. What is important is that they can get something in the shortest time. 80% of IT enterprises belong to this type. They require programmers to quickly familiarize themselves with business knowledge and then start to participate in project development.

Most of them are repetitive work, and programmers are doing basic adding, deleting, modifying, and querying work. In addition, these jobs are encapsulated by layers, and the technical aspects that programmers are exposed to are very narrow. In the long run, programmers with insufficient concentration will be affected by the surrounding environment. Some may choose to switch rows, and some may choose to do business and implementation. In fact, we should have the courage to choose at this time and stick to our own ideals. Of course, this requires the support of interest.

I will not express my opinion on this change. After all, people have their own aspirations. The topic of this article is the combination of Business and Technology. how to extract the core domain model between technology and business makes our technology more useful.

From the perspective of the company, we should learn more business knowledge, and the technology is generally put in the hands of some architects. We only need to learn to use the company's framework.

Technical assistance is used in business. people engaged in business always think that business is more advanced than technology. technical personnel should listen to them. This is a common phenomenon. At least the companies I have come into contact with are like this. They ask programmers to change what they want, because they do not understand the complexity of the program, and a little unreasonable may cause the overall structure change of the program, the workload may be several times that of development. Leaders may also say whether you can design a very modular, highly cohesive, low-coupling plug-in system or a new term. We may be speechless because they do not understand the technology? How can there be a permanent system;

In fact, the contradiction is that if our technical staff spend a lot of energy learning business knowledge, we will spend less time learning technology, then we will be tied together with the company. At this time, we have different perspectives. if you attach importance to your business, you may need the company to promote you or put your job in the hands of the company, if the company doesn't see you well someday, you will lose your job. If our technology is always ahead, I am not afraid that your company will not want me. I can live wherever I go. This sentence may be selfish, but I feel that programmers should learn to protect themselves.[Wang qingpei has all rights reserved. For more information, please sign it.]

If you really think that your leadership is worthy of your follow-up, you should study your business well. If the company really does not have anything worth your effort, Please study the technology well;

2: How programmers learn business

How should our programmers learn business? I think we should choose not to learn everything.

A company's business may be very simple and complicated. We need to choose system-related business, which one we want to learn, and the most important thing is to have the concept of business model in mind, the idea of modeling here can be viewed in "Domain-driven design".

Why is there a business model? In fact, this is a way to gradually cultivate our design capabilities. To learn business knowledge, programmers must be clear and cannot be vague, because these concepts must be embodied in the system. If we understand it as vague, then we writeCodeIt is also vague. When we communicate with our colleagues, our module may lead to ambiguity of other modules. At this time, the bottleneck will come.

When learning business knowledge, we must remember whether the overall structure can be reflected in the Code and whether the business model can be extracted;

Figure 1:

To learn business knowledge, we need to classify it appropriately and abstract the objects of a business online.

If we are good at expressing business in code, it is much better to use technology to implement basic functions. At least this is a design job. (Design capability reflects the technical level)

3: extract business models based on business and technology

When chatting with people who are engaged in domain models, they can feel a strong sense of model. They have a strict understanding of the business and cannot be vague. Why is it so meticulous? This makes their models more robust and stable. They are often very competitive and proficient in business and technology.

But unlike the business we see, they can make the business smooth over to the code. They can organize the business very neatly. We only need to know a little about the business and participate in project development. The code is completely constructed according to the business model. Once this person is familiar with an industry, he is an absolute expert in the field.

Summary:

In fact, a bunch of nonsense above is also a little bit of my recent sentiment.

Technology is the lifeline of our programmers. Only by taking an absolute advantage in technology can we save our job. Then we will promote our technology to a modeling realm, and then it will truly serve people. Thank you;