Talk about outsourcing, small business, medium business and big factory front-end experience

There are two types of outsourcing, human resource outsourcing and project outsourcing:

Front end number: < 3
Product type: The product is not very mature, relatively new.
Project process: imperfect, fast, tight, no fixed schedule.
Technology stack: No historical baggage, relatively new technology stack, no front-end architect or even high-level front-end.
Project security: Little additional consideration is given to security.
Infrastructure: Almost none.
System availability: There are few specific standards.
Front-end engineering: Use industry solutions, as quickly as possible.
Learning atmosphere: Self-study.

Front end: > 20 people
Product type: the company has its own mature products, there are a certain number of users.
Project cycle: fast, fast, fixed time schedule, busy time idle.
Technology stack: No historical baggage, relatively new technology stack, front-end architect or Teach Lead
Project security: Consider simple security issues such as SQL injection, XSS, CSRF, etc., and rely on third-party libraries.
Infrastructure: error monitoring, log collection, and code rollback. The obvious experience is that sometimes when you make a new feature or fix a bug, you accidentally overdo the previous code.
System availability: There are few specific standards.
Front-end engineering: Using industry solutions, standardizing and documenting, there will be precipitation of non-business related technical requirements.
Learning atmosphere: self-study + discussion.

Front end: > 50 people
Product type: Industry transformation, mostly internal products, such as some saas products, more internal use.
Project cycle: in the industry transformation, fast, relatively fast, roughly fixed schedule, busy, idle, or both quite idle.
Technology stack: Historical baggage, older technology stack, more technology stack, front-end architect or teach Lead.
Project security: We will regularly invite a special security team to perform security tests.
Infrastructure: There will be A/B test, data burial points. I will try my best to avoid mistakes, and the process is still not standardized. The obvious experience is that I dare not reconstruct, upgrade or rely on, change the system, or accept the pot, but I can run.
System availability: no or three 9’s
Front-end engineering: use industry solutions, use documents to do standardization and precipitation, lack of their own internal front-end customized chemical tool library, component library, etc.
Learning atmosphere: self-study + discussion.

Front end: > 50 people
Product type: multiple mature products, and become the industry leader or unicorn
Project cycle: two weeks iteration, the project is tight, relatively fast, roughly fixed schedule, busy time and idle time, there are project intervals.
Technology stack: There is historical baggage, the technology stack is newer, the technology stack is larger, there will be front-end architects or teach leads.
Project security: We will regularly invite a special security team to perform security tests.
Infrastructure: mainly configuration, tools, perfect infrastructure, would consider performance problems, can the customer found the problem before, found that part of the problem, can quickly positioning problem, and solve, obvious experience is have a special team to maintain these standards or operation process, principle and operating tools to work, to restrain people.
System availability: generally more than 4 9s.
Front-end engineering: combine documentation and tools to achieve standardization, such as code specification, code verification, code test coverage, etc., can precipitate some process scripts, code base, tools, experience, scaffolding.
Learning atmosphere: weekly sharing, understanding of various cutting-edge technologies.

Front end: > 50 people
Product type: a number of mature products, become the industry leader or unicorn, monopoly trend.
Project cycle: two weeks iteration, the project is tight and rapid, no project interval, great pressure.
Technology stack: with historical baggage, new technology stack, many technology stacks, there will be front-end architects or teach leads.
Project security: It will be checked by its own security team before release.
Infrastructure: Precipitation has become systematic, platform-based, and medium-based. It is possible to really use the platform to improve performance and limit human behavior. The obvious experience is that even without the maintenance team, the process can still exist and flow normally. Internal teams or outside vendors can rely directly on a service’s API to build a fully personalized application.
System availability: generally more than 4 9s.
Front-end engineering: Some sediments have become industry benchmarks.
Learning atmosphere: weekly sharing, understanding of various cutting-edge technologies.

The above conclusions are based on my own experiences or discussions with friends around me, and can be discussed in the comments section
In fact, it can be divided into more detailed, or there are not covered to the place, or each company has special circumstances, we do not have to be too serious conclusions.
There is no such thing as a good company or a bad company.