During this period of time, I was very busy, with a lot of public affairs and private affairs, and I was very tired, and I almost didn't even have time to read books. Taking advantage of this holiday, it's finally time. Today, I will briefly introduce the development process of our team.
1. Tuba Road
When it comes to Tuba Road, I always feel a bit ironic, the former Tuba Road is indeed no worse than the regular army! Hey-hey!
Tubalu's play style is flexible and changeable, and it is all based on his own practice.
In fact, every developer basically grows up through exploration. Especially in small companies, developers have a lot of autonomy and a wide range of skills.
In the past, when we were working on projects, in addition to a set of basic framework codes, we had to rely on ourselves. Basically, after the project manager has figured out the requirements for each project, the developers have to do everything else, such as requirements analysis, design, art, CSS, development, deployment, testing... basically all involved. As a result, almost every member of the team becomes an "all-rounder".
At this stage, the entire development process is relatively simple:
- The project manager conducts demand research and confirms the demand
- Developers develop prototypes on demand
- After many times of communication with customers, the prototype was confirmed
- Artists design the landing page and make several layouts based on the prototype
- Developers do system design
- The developer develops and sets the page according to the design and cutout of the artist. Among them, many effects have to be done by technicians themselves, including CSS, even simple PS pictures, etc.
- Developers deploy and test
- system online
- ...
Developers, you have worked hard, this project is entirely up to you, you continue to carry it, you have to withstand the pressure...
Every time I work overtime, I only see your figure...
2. Semi-regular Army SideSide
Regular army requirements can be high, but also not very flexible. Software development has become very difficult, and it is not very reliable to take the regular army route!
Later, we slowly stood beside the quasi-regular army, and gave ourselves a nickname: quasi-regular army SideSide
At this stage, the entire development process looks like this:
- The project manager still conducts demand research and confirms the demand, but the UE or UI will participate when necessary
- UE uses tools such as RP to design prototypes
- After many times of communication with customers, modify the prototype, and finally confirm the prototype
- UI is based on the prototype designed by UE, using PS, AI and other tools for page design
- After communicating with customers for many times, modifying the UI interface, and finally confirming the UI interface
- Page developers develop corresponding static pages according to the UI page design, including special effects such as menus and pop-up boxes.
- Business developers design and develop static pages according to their requirements and static page effects, and make static pages dynamic
- Business developers deploy test environments
- Testers test the system
- system online
- ...
Now, in principle, I recommend unifying the development environment to reduce the possibility of problems and improve development efficiency. If developers encounter technical problems, business problems, or have any suggestions, they can tell me directly, which can greatly reduce the risk of progress. Developers should try not to deal with the same type of problems or functions at the same time, and try to share common functions with everyone for mutual reference, which is highly efficient! Regularly understand the development of project members individually, and find and solve problems early; if the sheep are kept for too long, the more problems accumulate, the enthusiasm for development will be low, and the efficiency will also decline. Overtime is inevitable, and it is better to work less overtime to stay healthy Well, Kaifu teacher regrets working too much overtime back then...
(Please indicate the source for reprint: http://zhanjia.iteye.com/blog/1950180)