The report summary
1. Introduction
With the rapid development of information technology, a number of domestic cloud computing, database and other developers as the core users/customers of the rapid growth of the enterprise, developer ecological marketing, developer relations, technology brand and product promotion for developers such as exclusive groups, is becoming an emerging position.
In this context, SegmentFault Research Institute launched the “Research Report on the Status Quo of Chinese Developer Eco-Practitioners in 2021”. We conducted a survey on the status quo of the developer ecosystem in China, helping developers to better define their work content and goals, and obtain career promotion. We also provided reference for enterprise managers who are in the process of establishing or have established relevant departments.
This report integrates the observation and analysis of SegmentFault, industry-related research institutions, enterprises and business practitioners on developer ecology and developer eco-marketing personnel, and combines 891 precise questionnaire data to carry out an extended analysis and summary of the current situation of domestic developer eco-marketing personnel.
2. Research methods
1) Questionnaires and data analysis
- Scale: 891 valid questionnaires were collected
- The investigation covers the situation of enterprises and public institutions, see the Acknowledgements at the end of the article
- For the list of enterprises and institutions covered in the survey, see the Acknowledgements section at the end of the article
2) Interview with target objects
3) Interview with experts and visits to enterprises
Portrait of the Investigator
1. Geographical distribution of interviewees
This research report is mainly for Chinese developer eco-practitioners. From the perspective of regional distribution, the number of users located in Beijing, Shenzhen, Hangzhou and Shanghai is large (more than 5%), which may be related to the office location distribution of several cloud computing manufacturers, such as: Alibaba Cloud is mainly based in Hangzhou, Huawei and Tencent Cloud are mainly based in Shenzhen, and Baidu, Google, Intel, AWS and other companies have their China headquarters in Beijing.
Among them, Beijing accounts for more than 50% (56.57%), and the vast majority of technology enterprises have branches/headquarters in Beijing.
In addition, the survey results show that practitioners related to “developer ecology” have also begun to appear in new first-tier cities such as Wuhan, Xi ‘an, Suzhou, Changsha, Qingdao and Nanjing, which reflects the high-tech development of these cities.
2. Crowd portraits
1) Position of interviewee
This survey is mainly for developers relations practitioners, most of whom are managers/senior managers in the company, accounting for 45.57%, followed by specialists and directors/senior directors, accounting for 31.54% and 17.62%, respectively. This survey also covers some senior managers and assistants who have just entered the workplace. They accounted for 3.14% and 2.13%, respectively.
2) Age of interviewees
In terms of age distribution, this survey covers all age groups of working people from under 25 to over 46 years old. The 26-35 year old practitioners have become the backbone of the developer ecosystem industry, accounting for 63.64% of the total number of people in this survey.
3) Gender of interviewees
In terms of gender distribution, the male to female ratio of developer ecosystem practitioners is about 0.73 to 1.
Compared with the male and female ratio of traditional market operation practitioners, the male ratio is significantly higher; The percentage of women is significantly higher than the gender ratio in the tech/developer sector
4) Work experience of interviewees
In terms of working years, users with 5 years of working experience account for 50.51% and users with more than 5 years of working experience account for 49.49% of the total number of people in this survey. The number of the two parts is basically equal.
5) Education level of interviewees
According to the survey results, developers and ecological practitioners generally have a high level of education. Users with a bachelor’s degree or above account for 95.29%, among which 2.13% have a doctoral degree. Only 4.71% of the users have an education level of junior college or below.
3. The type of company the interviewee works for
1) The customer group of the interviewee’s company
Among all interviewees, 77.78% of users believe that the main business of their company is to B, 48.04% of users believe that the main business of their company is to D, and only 17.04% of users believe that the main business of their company is to C.
Typically, companies in TO-C businesses invest in the developer ecosystem, usually because the product itself is aimed at individual developers, or to promote the company’s technology brand or employer brand.
Respondents to cloud computing and artificial intelligence companies typically define their companies as B2B companies that generate revenue primarily by providing software services to businesses. They divide developers into regular developers (college developers, individual developers, enterprise developers) and IT Pros.
- IT PRO is usually a developer who has the decision-making power to choose the technology in the enterprise.
- Ordinary developers usually refer to enterprise technicians, university developers and individual independent developers doing development on the front line.
Preaching to enterprise developers can help them make better use of their products and increase product & brand awareness. Some enterprises define ordinary developers as mid-to-long tail customers, believing that they can indirectly influence the technology selection of the enterprise.
It has also become an important strategy for 2B enterprises in recent years to capture the minds of developers and make them loyal users of their brands, so as to influence the technical decisions of enterprises in the future.
Individual indie developers are generally not a key audience for 2B businesses.
All three types of ordinary developers are the focus of the open source business, and they can become users and contributors to open source projects. Often open source commercial companies will define their business as B2D.
In addition, there are a number of companies that traditionally we think of as 2B businesses that would also define themselves as 2D businesses. For Developers, By Developers, they think the developer experience is bigger than anything else. So, is the business 2D, 2B, or 2C? When interviewees make a choice, it is not only related to the actual main business of the company, but also related to the values of the company and interviewees’ personal understanding of the business.
2) Corporate culture of the interviewee’s company
More than 50 percent of respondents believe their company’s culture is the most technology-driven (50.28 percent), followed by a customer-first culture of 27.05 percent and a business-driven culture of 18.86 percent.
When the interviewee makes a choice, it is not only related to the corporate culture defined by the company, but also related to the corporate culture and values shown in the actual implementation.
Practitioner’s role, position, organization structure
1. The role of the interviewee in the company
1) Departments of the developer relations team
Of the interviewees, 40.07% of developer ecology practitioners belong to marketing, 20.88% belong to operations, 19.87% belong to independent developer ecology, 13.58% belong to production and research, 2.36% belong to strategic department or directly provide advice to CEO/CTO. Another 3.25 percent chose something else.
2) Job title of interviewee
Open Source Technologist, Developer Relations, Evangelist, Developer Marketplace, Developer Operations, Community Operations, Technical Strategy, Marketing, Community Manager, Technical Content, Technical Expert, Community Manager, CMO, Event Manager, Brand, User Growth, CTO, Product Marketing Manager, Product Manager
2. Organizational structure of the interviewee’s company
1) Number of interviewees in the company
The survey results on the number of companies show that respondents with a company size of more than 10,000 employees account for 40.18%, followed by companies with a company size of 500-999 employees and 100-499 employees, accounting for 25.48% and 13.58%, respectively. Those whose companies are smaller than 20 employees only account for 1.23%.
2) Number of developer relations team of the interviewee’s company
From the perspective of the number of developers relations team, some companies currently have no full-time staff, or only one person engaged in developer relations related work, accounting for 7.96% of the total number of respondents. The interviewees whose company’s developer relations team has more than 50 members are the most, accounting for 36.14%.
3) summary
By comparing the above data, we can find that:
No full-time personnel, or only one person engaged in developer relations related work, accounting for 7.96% of the total number of respondents; The total number of employees in the company is less than 100, accounting for 8.64% of the total number of respondents.
The number of the developer relations team in the company is more than 50, accounting for 36.14% of the total number of respondents; The total number of employees in the company is over 10,000, accounting for 40.18% of the total number of respondents.
The number of developer relations teams is positively correlated with company size.
The two options, with a developer relations team of more than 50 people and a company of more than 10,000 people, both account for the highest proportion among the respondents. It can be seen that “big companies” such as cloud computing companies and well-known foreign companies are still the mainstream force in the field of developer ecology.
3. Industry perspective
Do respondents think it is necessary to have an independent developer relations department?
In this survey, 85.86% of respondents believe that an independent developer ecology/relations department is necessary, while a small number of respondents believe that it is not.
Daily work analysis of interviewees
1. Performance appraisal and work objectives
1) Performance appraisal and work objectives of interviewees
The research topic for the work objectives of the practitioners is a multiple choice. A total of 3929 work objectives were selected from 891 valid questionnaires, indicating that the enterprise has diversified assessment indicators for the work of the developers and ecological practitioners, with each person undertaking 4.41 work objectives.
Among the job metrics, more than half of the respondents’ job goals include developer/technology brand influence, organization and participation in developer events.
More than 1/3 of the interviewees’ work objectives include developer user growth (community registered users, product users, new product purchase users), traffic of their own website/developer community, third-party community users/developer users/brand reputation in the industry (developer relationship).
Job objectives related to product sales (providing sales Leads, being responsible for revenue/market share, customer/user satisfaction and repurchase/renewal rate) are not the main job objectives of the developer ecosystem practitioners, accounting for less than 1/3 of each.
In addition, only 10.55% of respondents’ job objectives included assisting the product development department with product iteration, which was lower than our expectations as a department that worked on the front lines with developers and users, perhaps because this work was difficult to quantify and was evaluated as a key result.
2) Industry view: What do you think are the most important indicators that developers ecological practitioners should pay attention to?
In this question, respondents were asked to choose the single and most important core metric that they thought developers eco-practitioners should be concerned about.
The results of the survey show that people generally agree with the work goals of user growth and technology brand, but have low recognition of the work goals related to business revenue.
3) Summary and contrast
By comparing the actual work assessment indicators of developers and ecological practitioners with the only and most concerned core indicators in the eyes of interviewees, it can be found that:
- The work objectives related to user growth and technology brand are highly valued by enterprises and recognized by interviewees.
- The work goals related to business revenue are not valued by enterprises and accepted by interviewees. Developers should not directly bear the revenue goals of enterprises.
- The two options with relatively different research results are:
- Assisting the product research and development department in product iterative optimization has not been regarded as the main work result and performance assessment content, but it is highly recognized by the interviewees. As a department dealing with developers on the front line, enterprises should pay more attention to the linkage with production and research departments to promote product iterative optimization.
- The organization and participation of developers’ activities are highly valued by enterprises, but less recognized by interviewees. On the one hand, the activity itself should not be the goal of work, but the subsequent impact of the activity (such as technology brand promotion, developer user growth) should be the correct goal of work. In addition, the low proportion among single choices can also indicate the low importance among the only choices.
2. Main work contents of interviewees
1) Main means for interviewees to achieve work goals (specific work content)
The research topic of the specific work content of the practitioners is a multiple choice question. A total of 4284 work objectives are selected from 891 valid questionnaires, indicating that the interviewees have a variety of ways to achieve their work objectives, and each interviewee is responsible for 4.81 work contents.
In various jobs, more than 50% of the interviewees said that they would achieve their work targets through online and offline activity planning and organization, advertising and media cooperation.
More than 1/3 of the interviewees are in charge of community/community operations, event marketing planning, technical content creation and communication, customer case packaging and communication, etc.
3. How the interviewees manage the budget
1) Annual budget range
Budget investment plays a very important role in the ecological construction of developers, which also reflects the importance enterprises attach to the ecological development of developers. According to the survey results, 54.55% of respondents said that their department’s annual marketing budget for developers exceeds RMB 1 million.
Marketing budgets generally increase as businesses grow in size. Within the same organization, developer relations teams with different product lines have different budget ranges.
Among the interviewees with an annual marketing budget of more than 1 million yuan, 22.22%, 15.38%, 9.65% of the interviewees with an annual marketing budget of 1.01-3 million yuan, 3.1-5 million yuan, 5.1-10 million yuan, 10.1-20 million yuan, and 50.01 million yuan are respectively. 5.27%, 2.02%. The higher the budget range, the lower the proportion of respondents, indicating that marketing budgets tend to be in the hands of fewer people.
Can you guess which companies are the 18 interviewees who chose 50.1 million yuan or more?
2) Budget distribution
This is a multi-choice survey topic, with each person choosing 3.67 budget expenditure directions. Among them, more than 50% of respondents said that the current marketing budget is mainly used for the organization of online and offline activities; More than 1/3 of the respondents said that the current marketing budget is mainly used for marketing material production/external content cooperation, marketing materials printing production, user incentive, soft/hard advertising and media resources purchase; Less than 30% of users choose to spend their budget on industry research, marketing tools, and customer training. This research result, and the activity organization, marketing material production of the hard cost is also related to the higher.
4. The use of marketing tools by interviewees
1) Types of marketing tools frequently used by respondents on a daily basis
In the selection of common marketing tools (multiple choices), the choices are more equal. Top of the list are tools for making marketing materials such as H5/ posters. In the question “Difficulties in the Job”, some interviewees also said that the company lacked design resources. It can be seen that the use of “zero-based drawing tools” to make marketing materials has become one of the necessary skills for developers, ecological practitioners and marketing operators.
2) Examples of common tools used by interviewees
In the list of developer marketing tools you use most often, the following tools were mentioned the most
5. Internal and external cooperation of interviewees
1) Which department do interviewees cooperate with most in their daily work
Not surprisingly, there was a lot of collaboration between developer eco-practitioners and industry and research departments. Iterative optimization of the product requires developer operation personnel to sort out and feedback the opinions of front-line developers and users. In addition, the developer operations staff can’t organize technical events and meetups without the cooperation of the production and research team.
In addition, interviewees also cooperated with marketing, sales and business teams, such as jointly organizing online and offline activities and providing sales leads for sales/business teams.
2) Time spent in meetings per week
The survey results show that 17.51% of respondents have meetings for more than 10 hours a week, and 28.51% have meetings for 5-10 hours a week, that is, 46.02% of respondents have meetings for more than one hour a day on average. In addition, 53.98% of the users’ daily average meeting time is less than 1 hour.
3) Do interviewees interact directly with developers? Frequency is?
Developer relations/operations staff, a bridge between various departments within the enterprise and front-line developer users. According to the survey results, about 25.25% of respondents communicate with developers on a daily basis, and 67% communicate with developers more than once a week.
However, 33% of respondents still fail to communicate with top tier developers on a high frequency basis, which may be related to their organizational structure and division of labor.
However, we believe that in terms of the organizational structure and division of labor of the company, the work content planning should require close communication between developers ecological practitioners and developers.
4) Will interviewees directly interact with customers? Frequency is?
More than half (54.43%) of the interviewees communicate with customers less than once a week, indicating that customer relations and after-sales support are not the main work of developers’ operation staff. In addition, 45.57% of the interviewees may also include some enterprises whose main business is 2C business. Customers are developers.
5) Will you be invited to participate in the company’s product/business strategy meetings?
“Developers win the world”, developer strategy is very important for technology-oriented enterprises, but also has a certain impact on the direction of the company’s product/business strategy, 77.66% of the respondents said that they will/occasionally invited to participate in the company’s product/business strategy meeting.
6. Challenges in the interviewees’ daily work
1) Challenges in daily work of interviewees
More than a third of respondents reported that day-to-day challenges were due to mismatches between communication budgets and goals, a lack of systematic understanding of product technology, frequent changes in business goals, and a lack of understanding of developers.
Among them, the mismatch between the communication budget and the target occupies the first place, with 41.53% of respondents choosing this option. Secondly, lack of systematic understanding of product technology and frequent changes in business objectives, accounting for 38.38%; 34.57% of the interviewees said they lacked understanding of developers, 29.52% said they had high assessment pressure indicators, 21.44% said they were insufficient in marketing and creativity, and less than 10% said they had inadequate service quality of suppliers or had other challenges.
2) Core pain points of interviewees’ work
About the core pain point of the work, we also interviewed several related practitioners anonymously, including the developer community leader of “Dachang”, and the open source community manager of small and medium-sized enterprises
- The company fails to correctly view the relationship between developer relationship work and revenue growth of the company. The company pursues too much short-term returns, which leads to the unstable strategy of the developer and the failure to make long-term investment. After 2 or 3 years of community investment, the company gives up, and the previous efforts go to waste.
- The company only pursues the growth of the number of registered users of developers, but does not pursue the quality of users. There is no multiple evaluation system, and the work is not recognized.
- Team members are mainly marketing operation professional background, not familiar with the company’s products and technologies, not understanding the needs of developers.
Analysis of respondents’ recognition
1. Is the interviewee’s work understood or recognized by other departments?
Most of the respondents (83.84%) said that their work could be understood or recognized by other departments, but 16.16% said that there were some misunderstandings or communication barriers between them and other departments, of which 0.67% were fully understood.
Developer ecological marketing, developer relationship, technology branding and product promotion for exclusive groups of developers, as emerging positions, may be difficult to disassemble, quantify, and not be understood and recognized in the early stage, as well as lack of diversified evaluation system.
Taking open source projects as an example, some commercial companies in China are too keen on the number of STAR projects. However, in the GitHub 2020 Digital Insight Report produced by Mr. Wang Wei, director of Open Source Society and teacher of East China Normal University, his calculation formula of “developer activity” is given, and the number of STAR projects does not reflect the developer activity. It should not be the primary goal of the open source community manager.
In addition, there is no objective and comprehensive evaluation index for the operation of enterprise developers, which can help other departments and company leaders and decision-makers better understand the work of developer operation.
2. Influence of the interviewee’s position
The interviewees gave an average of 6.7 points in terms of the influence of their positions on corporate strategy, product strategy and development and the degree of internal importance.
Professional Development of Practitioners
1. Past professional experience of interviewees
1) Past professional experience of interviewees
With the development of cloud computing and artificial intelligence, more and more people are joining the developer operation work. Most of them are transferred from other positions and have rich working experience.
- 54.10% of the respondents were previously engaged in marketing (marketing, public relations media, events and exhibitions, advertising, etc.), ranking the first;
- 93% of respondents were previously engaged in operations (product/user/content/data/community operations), ranking second;
- In addition, 9.20 percent had previously worked in sales, 6.06 percent had previously worked in production and research departments, and 2.13 percent had no previous work experience in other positions.
2) Reasons for interviewees to adjust their jobs
In the survey on the circumstances under which they would consider changing their jobs, 891 valid questionnaires selected 2397 options, and each person chose 2.69 reasons for job-hopping.
More than half of the interviewees expressed that they would like to adjust their work when their personal abilities cannot be given full play and they do not agree with the development prospects of the company/product line, accounting for 65.43% and 52.75% of the total respondents respectively. The development of the company/product line and personal development complement each other, business and personal achievement, it can be seen that the vast majority of interviewees value personal development space most.
Among the influencing factors of the interviewees considering job adjustment, more than 1/3 interviewees said that they would consider job adjustment when they were dissatisfied with salary, lack of work enthusiasm or lack of management leadership, accounting for 49.61%, 37.93% and 33.78% of the total interviewees respectively. 29.52% of respondents said they would consider new job opportunities due to a lack of voice and a sense of business involvement.
3) Average job-hopping frequency of developer ecosystem practitioners
In terms of job-hopping frequency, respondents who have worked for 1-3 years job-hopping 1.26 times on average; For interviewees who have been working for 3-5 years, the average job-hopping frequency is 1.76 times; For interviewees who have been working for 5 to 10 years, the average job-hopping frequency is 2.30. For those who have been there for more than 10 years, the average number of job changes is 3.27.
2. Career development plan of interviewees
1) Interviewees’ satisfaction with their current jobs
2) Career development plan of interviewees in the next two years
From the perspective of career planning in the next two years, 78.68% of users expressed the hope to continue to struggle and improve in their current positions, indicating that employees in this industry generally have a strong ambition to forge ahead.
11.56% of the users said they were satisfied with the current situation, and 9.76% of the users planned to change their career direction, which may be related to the higher requirements on technical understanding of this position.
3) What the interviewees considered the most important competencies of the relevant practitioners
The positions related to developer ecology require a high level of technical understanding, so “a good understanding of products” ranked first in this survey, with 23.46% of respondents ranking this ability as the most important ability for developer ecology practitioners.
In addition, more than 10% of users think that creativity and problem-solving ability, marketing planning and brand communication ability, a high understanding of the brand, coordination with colleagues and cross-department cooperation ability are also very important, with 11.34%, 11.34%, 10.44% and 10.44% of respondents respectively choosing these four abilities.
Although it is widely believed that the position requires some skills, “having a technical/science background”, as the single most important ability, was not chosen very much, accounting for only 9.54% of all respondents.
The respondents who chose empathy, communication ability with customers, content output and copywriting ability were all lower than 5%, accounting for 4.71% and 1.01%.
4) How do interviewees improve their personal skills
According to the survey, paying attention to industry media, WeChat official accounts, following the industry, learning from marketing schemes of peers, maintaining cooperative relationships with communities/media, and attending training/salons/forums are all common methods for developers to improve their personal skills. More than 1/3 of the respondents chose each option.
We spoke to 20 practitioners anonymously, and they said:
- Daily attention to SegmentFault, InfoQ, CSDN and other technical media, on the one hand to understand the technical information, on the other hand can also follow the industry trends, peer trends through the technical media.
- When making the annual budget or planning major marketing events, I will pay close attention to the dynamics of peers and learn from industry cases.
- Visit the tech community or media regularly. They know more about developers and can give professional advice on developer operations and marketing activities.
- At present, there are few activities for developers eco-practitioners in the market. Participating in training/salon/forum usually refers to participating in technical activities of the same industry and the industry. China Developer Eco-Summit is a rare event in the industry.
5) Career development advice for developer eco-practitioners
The digital age is the best of times for developers, and it’s also a golden age for developers eco-professionals. The road ahead is good, but the road will not be smooth. On the one hand, the continuous innovation of technology requires the continuous self-learning of developers and ecological practitioners; On the other hand, in order to make developers’ relatively long-term value recognized by the company, practitioners need to straighten out complex relationships, cooperate or even lead different departments of the company, and realize the scale growth of users and the expansion of technical influence. After working as a developer for more than a year, I have not only felt the bright prospect, but also felt the difficulty of the journey.
— Meng Jinyu, head of developer relations at Aliyun
At the core of building a “developer ecosystem” is empowering developers to solve user problems with software. As a practitioner of the “developer ecosystem”, I remind myself of the following three questions:
2) Whether our services continue to improve developers’ experience and help developers achieve “business value”; 3) Whether our strategies align with corporate goals and help enterprises achieve “vision and mission”.
I have a long way to go, and I hope we can work together with “developer eco-partners”.
— Huang Jijia, head of developer marketing for Google’s ecosystem business group
In this age of open source acceptance, the career of developer operation, or Devrel, is a promising one. First of all, the position is not a low level of expertise. It requires an understanding of developers’ preferences, technology developments, marketing, and even some coding skills. At present, open source projects in China are more and more recognized by the capital, and the reserve of open source operation talents in the market is far from enough, so it can be said that the career prospects are broad. I’m studying, but I’ve read a couple of books, and I’d like to recommend Cathedral and Market and The Art of Community Operation to you.
— Yao Wei, general manager of PingCap Community Business Unit
Learn: The life cycle of technology update is between 2.5 and 5 years. You should constantly update your understanding and cognition of technology, which can be kept at the same frequency as engineers.
Please be curious: a more diversified and open understanding of the relationship between communities, the core of other people’s products, not limited to their own products and industry vision, to be sensitive to the periphery;
Value your experience: Don’t think what you learn in your current community is “unimportant” or feels “unrepeatable.” Communities are not trivial, and operations are rarely “unique.” The entire ecosystem of the tech community is evolving, and it’s hard to see the value of “feel” in the repetitive work you’re doing today, and it’s hard to predict whether the personalization of the community you’re currently running will be the future. But cherish, reflect and sum up all your experiences, and one day you will understand that the past is a prologue.
— Ze Yuan, general manager of community ecology at sound-based Agora
I’ve always believed that there are two ways to do developer ecology, one is to be on the sidelines, and the other is to be in the middle. I always suggest that only by staying in the community and feeling the pulse of the community can we do a good job in ecological operation. An added benefit of spending time in a community is that you’ll be able to expand your network and make new friends, which will give you a broader career path.
— Zhuang Bianwei, Huawei cloud product expert and president of Open Source Society
Students, if you choose the career direction of developer operation, then congratulations, you have great vision!
This is a very high requirement for comprehensive ability of the occupation, not only to understand the market, but also to understand the operation, but also to understand the product technology, really good threshold is very high, such talents are scarce in the industry.
Of course, the challenges we face are also great. Suggestions to strengthen our abilities are as follows: 1. 2. Construction of marketing thinking; 3. Enhance strategic perspective and conduct community operation from the perspective of technological ecology.
At the same time, the most important thing is a willingness to dive in and understand the technology and the business, enjoy working with developers, and take pride in empowering others.
— Guo Yue, former head of developer marketing at JD Technology and former head of Apollo developer community
In fact, it is very difficult to “overtake in corners” to improve professional skills. It requires more practical thinking and practice. I personally hope that developers market operators can have more love, be active and contribute to the community in their spare time, and keep close communication with developers at work. I personally participate in a lot of work in the open source community in my non-working time, and have a better understanding of open source through my contribution, which is of great help to my daily work.
From the perspective of career development, in addition to solid work, we should also learn to “manage up”. According to the survey results, many interviewees said that the strategy of the company developers is unstable, the business goals change frequently, and the goals do not match the budget. Striving upwards for more resources to achieve work goals is also an essential skill for every working person.
— Jiang Bo, SegmentFault COO Partner, Deputy CEO of OpenSource
3. The company with the best developer ecology in the eyes of practitioners
The end of the
1. Contact us
If you have any questions, suggestions or comments about this survey, please contact us through the following channels:
Website: https://segmentfault.com/ Email:[email protected] weibo: SegmentFault WeChat number: public SegmentFault WeChat public number: developers ecological LinkedIn: https://www.linkedin.com/comp… Twitter:https://twitter.com/segment_f… Facebook:https://www.facebook.com/Offi…
2. Authors and contributors
producers
SegmentFault is a leading new generation developer community and technology ecosystem service platform in China.
Author and Contributor
Content Designer: Jiang Bo, SegmentFault COO Partner, Deputy CEO of Open Source Society, Founder of China Developer Ecology Alliance
Lin Xu, Yun Xing, Lulu Guo, Yuan Liu, and Shang Wang also contributed to the survey.
3. Thank you
4. Report download
For the full report, please follow the WeChat official account [Developer Ecology]
