Summary of atitit. Improved software development efficiency O5
# --- Platform-based and componentized 1
# -- CBB public module construction 1
# --- Summary of best internal process methods and practices 2
# --- Internal knowledge system construction 2
# --- Problem QA Library Construction 2
# --- Internal framework/standard class library/API/service Library Construction... 2
# ---- Development toolkit and configuration construction... 2
# --- A collection of code generation and code conversion tools, and interoperability 3
# ---- Pay attention to the new features of development languages, class libraries, frameworks, and tools, and add them to our internal frameworks. 3.
# --- Code input method 3
# ---- Hot deployment hot Update 3
# ---- DSL & 4gl, script-based dynamic 3
# ---- Selection of multiple language platforms and architectures 3
# ---- Built-in advanced business data structure and operations 3
Half product/purchase + secondary development 3
# --- Large-scale outsourcing Management 4
# --- Contract system, discard allocation system 4
# --- Three-hour continuous work point. 4
# ---- Flexible work + suitable Soho 4
# ---- Staggered holidays, compensatory long holidays 4
# ---- Step-by-Step Team 5
# ---- SSD + large horizontal screen display, dual-host 5
#==--- Select a Work Location 5
# --- Working season 5
# ---- Reduce waste on the road
# ----- Centralized development 5
# ---- Print Document 6
# ---- Code snippets-code library construction 6
# -- Rest Zone 6
Author's old WAA paw attilax ailong, email: [email protected]
Reprinted please indicate Source: http://blog.csdn.net/attilax
# --- Platform-based and componentized
Business Development Platform> General Development Platform
# -- CBB public module construction
Including the front-end interface, controls and general components can accumulate.
# --- Summary of best internal process methods and practices
Convention is better than Configuration
MVP MVC
Cs> BS
ODB MySQL Oracle
Functional Programming
Process-oriented (statement), API-oriented, object-oriented, technical components, and business components (business modules) "To component/platform/service-oriented software architecture is a major way to improve efficiency ..
Business Flow graphics (technical components already exist .. However, the business may be unique .)
Set + secondary development
# --- Internal Knowledge System Construction
1. Unlock by file name.
2. Unlock by file content ..
# --- Problem QA Library Construction.
# --- Internal framework/standard class library/API/service library construction...
Self-developed platform library and Development Framework (verified, so faster)
# ---- Development toolkit and configuration construction ....
Active Database, socket connection spam Management
# --- A collection of code generation and code conversion tools, and interoperability # ---- pay attention to the new features of development languages, class libraries, frameworks, and tools and add them to our internal frameworks. solidified. # --- Code Input Method
# ---- Hot deployment and hot update # ---- DSL & 4gl, script-based Dynamic # ---- selection of multiple language platforms and architectures # ---- built-in advanced business data structures and operations
Half product/purchase + secondary development
# --- Large-scale outsourcing management # --- contract system, discard allocation system
After being divided into specific function points, contract the function points to the project team members. If the number of members is high, the salary will be high, and the performance will be linked ....
You can set different performance points based on different difficulty and time ..
When assigning a task, the greatest program can avoid human factors for task allocation .. Then the members can exchange functions with each other.
# --- Three-hour continuous work point.
Generally, 8 hours of continuous work is inefficient... A person can only concentrate on three hours .. So every three or two hours is a good practice...
# ---- Flexible work + suitable Soho
5 days a week to work in the company, it is a huge waste of resources, a week only takes 2 days to go to OK... 2 days a meet... the best...
# ---- Incorrect holidays and compensatory long holidays
For example, if you do not have a holiday within one month, you will go all out for the last 30 days of the month .. Then, take a 10-day long vacation. By the way, you can travel and relax .... Cancel the fixed 5-day working system.
... Working hours can be 12 hours a day, and overtime pay can be used to balance the situation, or a long compensatory break can be performed...
# ---- Step-by-step team members
# ---- SSD + big horizontal screen display, dual-host #=--- select a work location
It is best to have a beautiful environment. The seaside, the lake, and the forest edge are good working environments ,.. Greatly increasing the efficiency of people's work ..
# --- Working season
For software development, winter is the most efficient season .. Because it is cold outside, you cannot go anywhere .. Staying at the computer will be warmer. Oh .. Therefore, it would be best to select a work location to the north and south poles. Oh...
# ---- Reducing the waste of traffic on the road
Two or three hours of work every day is a big waste. It is not better to put these precious time in software development .. On the other hand, commuting is so frustrating and energy-consuming...
# ----- Centralized development
Place remote personnel in one location for development, reducing the loss of communication...
# ---- Print documents
Print out the corresponding document and read it at any time, which can greatly reduce the form switching ..
# ---- Code snippets -- code library construction
# ---- Use sleep instead of Shutdown
The computer should be set to sleep .. The restart speed is very fast... And the working status will not be lost
# -- Rest Zone
Exam:
Why did a tiered team win the all-star team's tiered team?
[Thesis] Why did a star team lose? _Baidu document store .htm
Summary of atitit. Improved software development efficiency O5