QCon 2015 Reading notes-team building

QCon 2015 reading notes

QCon 2015 read notes-Mobile development best Practices

QCon 2015 Reading notes-team building

dialogue between China and the West: five theory and practice of team management-Sechin, Fei (today's headline, LinkedIn)

Two people are actually more experienced, from the first-line internet enterprises at home and abroad.

Sechin: Microsoft-"Baidu-" Cool News (entrepreneurship)-"Today's headline

FEI: Cool News-"Baidu-" Amazon-"LinkedIn

Combat one: Job interview

• Source: Internal Push, LinkedIn
• Likes: Smart, curious, passionate, communicative
• Do not like: unwilling to learn, not in line with corporate culture
• Technology! Very few purely managerial positions

Combat two: Team structure

• Re-work, efficiency
• Light Title
• Flat
• Project-Structured
• Cross-departmental communication: To ensure the understanding of the objectives, communication meetings should be less suitable for more

Combat Three: System

• People: Accelerating talent growth and controlling organisational complexity
• Tools: Introducing Advanced tools

Combat four: Salary and performance

• Base + bouns + option/stock
• Salary Increase: Reduce the impact of company performance, increasing the impact of market prices
• The benefits of grounding gas: meals, room repair, mobile phone

Combat five: outside of work

• Team Building: Hacker contest, brainstorming, Team buiding, open Office

from engineer to leader-Liu Pingchao (American Regiment)

Liu Ping-chuan explains how a technician slowly transforms into a leader process, which is very useful for reference.

1. Baidu has AH

Everything starting from scratch-"technology trend-" Dudangyimian (interview, with people)

Flowering: Building user behavior System, Qwrap JS Library

2. Philharmonic Live

The idea of recruiting: quality is higher than quantity, and everyone hires someone stronger than ourselves to be a giant company.

The story between design development and product manager.

3. Baidu Fex

2013 60 people, covering the basic front-end research and development work.

Technical team, no top-down KPI, direction is not clear, lack of innovation.

Some of the changes made:

• Positioning: Clarifying the direction of doing things
• Business model: Return technology to market value
• Advocating open source

Several phases should focus on things:

• Engineer: The emphasis on technology
• Mentor: Emphasizing technology, focusing on others
• Manager: Responsible for the top and bottom, emphasizing the achievement of tasks and plans, time and energy in recruiting and team
• Leader: Vision, accomplishing, making, educating

build a high-quality technical team-Levin (UCWEB)

Start with the code: Technology Cut-in, based on their ability to gain voice and influence

Guide Code Specification landed: The collective force to constrain

Expanding specification content: Introducing software Development guidelines

Control the technical debt.

Open Working environment

QCon 2015 Reading notes-team building