Practice introduction of traditional industry internet era

Internet era: Service-based division of MicroServices by duties

PHP front-desk system rapid development, continuous delivery
Java Backend Service stable, sturdy and reliable

Simple, merging, decoupling, and clarity

Call log monitoring visualization: Call stack

Invoke log monitoring: real-time call tracking

Automating Deployment

? Interface Automation
? Jenkins Continuous Integration
? One-click Deployment, Automatic Publishing
? Multi-environmental support, development environment, A/BTEST environment
? Security Isolation Protection Audit
? Quick rollback mechanism

Schema abstraction separation, separation and separation

? Front-end component: Angular.js+require.js
? Back-end lightweighting: tiered development
? Service miniaturization: Atomic service splitting
? Interface Automation: Interface Automation testing, inspection
? Operational standardization: Intelligent Monitoring, automatic deployment, release

Research and development system construction

Human tool Process

Focus on the business, adjust the rhythm in time? Too many business requirements, after six months of development scheduling
? No time and effort to do infrastructure
? Work overtime every day, very bitter force
? Zooey change demand, moving mouth fast development to hands!
-------------------------------------------
? Business priority, clarity of urgency and importance
? Gradual extraction of staff building infrastructure
? Focus on business planning and system planning, real-time change adjustment
? Full and effective communication, unity
? Result oriented, let everyone become master

The balance point of technology, business and management

? Technology House focus on technology, do not understand management!
? The team is inefficient and the atmosphere is not harmonious.
-------------------------

? Reasonable time allocation, management authorization
? Enhance team strength in real time based on business growth
? Specify a schedule and move forward by milestone
? Everyone is a product manager thinking

Team Core: People

Product visionary- People who can understand the needs of the market
designer- who can design a good user experience
hacker- who can solve a program problem quickly
hustler- can solve all the other problems quickly.

Communication

? The collision of ideas and thinking, the inevitable friction caused by the rapid aggregation of different backgrounds
? Forming a virtual project team, breaking the gap between departments
? Active mouth on mouth communication, refuse mail, QQ,
? One to one non-regular communication
? Different people with different communication skills

team motivation and achievement

? Technical man's plot, sense of accomplishment above all
? Value orientation, spiritual motivation
? Bread and milk, and the material must keep up
? External borrowing Force incentive
? Integral System Management
? To Okr instead of KPIs, step
The OKR full name is the objectives and key results, which is the goal and critical results approach, and OKR is a set of management tools and methods for defining and tracking goals and their completion: 1999 Intel invented this approach and was later promoted by John Doerr to Oracle, Google,linkedin and other high-tech companies and gradually spread out, now widely used in it, venture capital, games, creativity and other projects as the main business units of large and small enterprises. OKR solves the various shortcomings of the KPI. First it is separated from the performance appraisal, and the performance assessment is given to peer review (equivalent to a 360-degree evaluation by a Chinese company). Then it emphasizes that key result must obey Objective, so if you write on Objective to let the user like our products, but you actually execute Key result means violate this point, anyone can see, naturally you do also only harm no good. Since Key Result is only used to serve Objective, there is no need to set it up and enforce it like a KPI. You can change Key Result as you do, as long as they still serve the original Objective. In fact OKR the most important role is to help you "stay Focus","stay focus" can help you "make impact" (of course, some people do not have focus can have impact, or have focus do not have impact).

Culture

? Culture is the most solid tool, culture first
? Team culture, core values, sense of belonging
? Engineer culture, technical productivity
? Sharing culture, internal sharing, external sharing
? The transfer of culture, precept

Personal growth

? Repair the computer, make a good network, sell the Moe, eat the loss, point out the direction, endure grievances
? Know how to share and give up the central idea
? Keep exercising every week
? Daily reading, Summary, reflection, improvement
? Deep thinking is more important than hard work

First here today, I hope you have a reference, you may be interested in the article:

Build efficient research and development and automated operation and maintenance
IT Infrastructure planning scenario one (network system planning)
Customer analysis process for catering industry solutions
Purchasing strategy formulation and implementation process for catering industry solutions
Business design process for catering industry solutions
Supply Chain Demand Research checklist
Evolution of real-time measurement system of enterprise application performance

If you want to know more software, System IT, enterprise information information, please follow my subscription number:

Petter Liu
Source: http://www.cnblogs.com/wintersun/
This article is copyright to the author and the blog Park, Welcome to reprint, but without the consent of the author must retain this paragraph, and in the article page obvious location to the original link, otherwise reserves the right to pursue legal responsibility.
The article was also published in my Independent blog-petter Liu blog.

Practice introduction of traditional industry internet era