当前位置:网站首页>Some thoughts on new company after job hopping

Some thoughts on new company after job hopping

2020-12-07 08:11:39 Coffee maker (k.f.j.)

   Recently, I changed my job to a small company which has been in business for many years , Bring a small front-end team .

   For more than a month , I'm mainly familiar with the business , Maintain old code , Write new business, etc , During this period, we also found all kinds of problems in the current team , I'm going to transform it in the next few days .

   The next small goal for yourself is , Change the chaos , Improve work efficiency , The team is more stable and standardized .

  

One 、 Adapt to the new environment

1) Rules and regulations

   First of all, adapt to the company's rules and regulations , The main thing is to get used to commuting time , This is different from the past , I was supposed to leave at the right time . Now, , I'm busy every day , I don't know when I'm off duty .

2) The new role

   The second is to adapt to your new role , The new company has a lot more to do than the old one , It used to be quite idle , But now it's different .

   And lead the team , The level of consideration has to be a little higher than before . You can't just think about your personal development , More about team development , Responsible for everyone on the team .

3) Development mode

   The next step is to adapt to the current development model , The last company only did H5 Related matters , That is to do some effect 、 Pure front-end work like applets .

   And there are some back-end tasks involved , use Node Made the middle layer , Integrate all kinds of data , perform Redis cache , Sometimes you have to manipulate the database directly .

   It was a little uncomfortable at first , Not only to learn to use terminals , You have to know how to check all kinds of problems by looking at the log .

4) Business logic

   Finally, be familiar with business logic , The premise is to run the project , Know how to modify .

   At present, the company lacks all kinds of documents , A lot of information can only be understood through the code after the employee leaves the company .

   For the convenience of debugging , Specially built unit test ( Main tests Node Aspect code ,Mocha+Chai+Supertest), This can guarantee the code quality , It is also convenient to understand the function of a function 、 The value of a variable, etc .

   There are a lot of businesses I don't know about right now , The future will often encounter . For these unknown businesses , In addition to the passive encounter to understand , You can also take the initiative to get to know with the relevant persons in charge of each group , Save against a rainy day .

5) difficulty

   The ancestral code is still running , The code is written in a mess , And many services are no longer maintained , But due to a lack of documentation , It is difficult to modify easily .

   Lack of personnel , Every day I'm tired of repairing all kinds of things BUG, And all kinds of miscellaneous things , It takes a lot of time to look at the code 、 Logs and databases , What you plan to write or do is often not done on time , It's hard to reach a balance . Although working overtime in the short term can solve , But in the long run, we have to add staff .

Two 、 Make the rules of the game

1) The front and rear ends really separate

   At present, the company's requirements for the front end are a little high , Both the mainstream front-end technology on the market (HTML and CSS Is a must , also React、Vue etc. ), Experience in back-end development , Such as operation MongoDB and MySQL etc. .

   Several employees have left the company for these reasons . In the future, if you still hire people like this , There will be a lot of obstacles , After all, there is no condition for a large factory .

   The front end will be responsible for a relatively large background management system , If it is some simple query update database statement , In fact, the complexity is nothing , It's just a matter of time .

   But the front end also has to deal with the amount sensitive information , This still needs to be handed over , After I came here, I discussed the plan with the big guys in the back end , To really separate , People in the back-end group also responded positively , But the transition process will be quite long , After all, resources are limited .

   In the future, the data source will be provided by the back-end server group as much as possible , The front end does the work of data integration and page effect , Try to be professional .

2) Unified technology stack

   At present, some technology stacks on the front end are old , Some of the active pages even use jQuery Make , This limits the development of team members .

   So we plan to unify the technology stack , Move subsequent projects to Vue or React These are the mainstream libraries at present , It's also good for the self-development of team members .

3、 ... and 、 Complete all kinds of documents

1) Technical documentation

   When I entered the new company , An old employee is leaving , He knows a lot about business , So we arranged for him to record as much as possible to the intranet Wiki in . The documents are not complete , But somehow there's a prototype , The future is going to be complete .

   Currently, the front-end Group maintains multiple projects , These projects also use different technology stacks .

   For example, the foreground of the backstage management system uses UmiJS+DvaJS+Ant Design+React, The backstage uses KOA2+NodeJS+MySQL+MongoDB.

   I spent some time and energy to explore the operation process of these two projects ( I drew some flow charts ), The technical details are also summarized , Reduce the difficulty of understanding for the new partners .

2) code annotation

   Future words , Also need to improve the source code of various comments , Many of the current functions and components are not annotated , You can only read the code line by line to understand , It's a lot of work .

   The company also plans to use tools ( for example swagger) By writing notes , Automatically generate interface documentation .

3) All kinds of business

   Other groups should also have relevant documents , There needs to be a guide page in the future , Jump to the relevant business . If not , We need to find a consortia , Let him arrange for someone to make up for it .

  

 

版权声明
本文为[Coffee maker (k.f.j.)]所创,转载请带上原文链接,感谢
https://chowdera.com/2020/12/202012070808599163.html