Technical team background judgment

At present, there are as many projects as dogs and as many startups as chickens.
Most are just a group of people, not a Team.
First of all, the model that 99% of the companies follow:
1. After the renderings of the requirements (maybe based on the functions of other peers to achieve self-confidence optimization), they will be directly thrown to the programmers... No matter what means and methods the programmers use, in short It can be solved perfectly, and the finished product can be written.
2, the finished product.
On Demand - Direct-to-finish mode.
Secondly, the energy and time allocation of the twenty-eight rule is not made for the realization of the project.
It is necessary to distinguish the core from the non-core. Generally speaking, when the project progress is stuck, most of them are blocked from the core implementation or the communication of the project structure is broken.


If you manage development without even thinking about core and non-core implementations, or don't know where to start - then the person in charge of the team - is definitely a rookie.
Therefore, a child with a little technical background will not obey the constraints when entering such a company.
In the same way, having such a boss on the stall is almost like falling into a pit.


The project development team with many people participates, the vision of the leader and the mechanism to deal with the difficult points in the development directly determine the progress of the project.

If the so-called technical team leader is directly on the job... then it can only be hehe-it can be roughly determined that this big guy belongs to the programmer who grew up with human flesh.


Technical team level division (personal sorting, if you are not satisfied, just ignore it):


Primary: Small outsourcing company, without its own core framework, there are hundreds or thousands of so-called finished products based on open source projects.
The development is only for secondary design and development of framework-based functional modules, and developers usually only give requirements + front-end art, and programmers are only responsible for perfecting all the required function implementation codes according to the renderings + front-end HTML effects.
This model is also used by most small startups.
As soon as you encounter a development problem, you will immediately - the so-called technical team can't find the north, and finally the boss will force the so-called CTO to join... Keke


Intermediate : Usually derived from the junior technical team, this kind of so-called technical team , Because of the years of research and development.
Self-confessed to understand the program, so let them recognize them.
They have been in for 3-5 years and screened out some good classic code implementations as technical background.
It can self-improve the open source framework + have its own functional finished product sample library. When doing secondary development, it can quickly assemble the code directly on the basis of its own code base. A better leather bag company is at this level.


Advanced: Project development, further documentation. There are not separate front-end requirements documents, renderings, and functional design processes, etc., and distinguish the core code.
The project can achieve relatively accurate research and development, and the energy and time can be allocated according to the 28 rule. Ali, Baidu, and Sina are similar.
In the early years, Ali was also not good at technology. He recruited technical executives from large companies and finally found that it was not very grounded.
The root cause of the lack of grounding is that executives directly follow the management model of others and directly develop documentation and standardization, but ignore the differences in individual perceptions of technology.
If 9 adults can't understand the order, it's bullshit.


Peak level: project research and development, follow the route of software engineering documentation, and any technical expert who leaves office will not cause much suffering to the company. Anyone, refers to—for example, the title in Baidu, the highest is a scientist, if a person of that level resigns and starts a new search engine, it will not cause any catastrophic consequences for Baidu, then Baidu’s software development Documented management as well as very perfect. .... As for how it works in reality....
So far, I can be sure that Oracle is doing that. As for domestic software R&D companies, the documentation is not very good.
Go directly to the online documentation of Sina, Baidu, Tencent, and Ali's secondary development interface, and you can see it at a glance.
Sina prefers foreign cognitive views, while Tencent's documents seem to be more suitable for Chinese people's logical cognitive habits.