Advanced process: the independence of programmers to do projects

The first stage ： Coding machine

This is the lowest stage , Programmers get detailed design documents , Many method interfaces have been defined . Refactoring some code , Write some implementations , Call some established API, Then spend a lot of time testing in various scenarios . From the work done , This is not a programmer , most , Just a coder with excellent coding skills . Because it almost kills all creativity , But this is very common , For example, in some Japanese outsourcing companies , That's all. .

The second stage ： Independent implementers

Programmers get only rough design documents , Perhaps a list of external interfaces is indicated , There is also the framework and infrastructure API, The requirements have been clarified , The next thing to do is to give full play to your intelligence and design the software implementation , Write the code , The test passed . This work can be done in a quiet and independent environment , Because nothing is not clear enough , Those parts that are not clear , project manager 、 The architect and product manager have done it . In such an environment, many things can be born OO Excellent design 、 Programmers with clear and concise code , But this is always just a incomplete project . Many novice programmers start from this stage , But if programmers can only design at the code level 、 Coding and testing , Not a complete programmer , Maybe not even half .

The third stage ： Project communicator and controller

Programmers and requirements engineers , Even customers clarify their needs , Analyze the feasibility ; We need to analyze the technical difficulties in the design project by ourselves ; Participate in deciding and managing iteration cycles and schedules ; Organize and participate in the operation tracking meeting within the project team . Things other than coding will take some time , Most of this time comes from the cost of communication . if , If the importance of communication has not been clearly seen in the first two stages , So at this stage , A programmer who can't communicate well , It will become the bottleneck of the operation of the project team . At least half of the domestic software companies' programmers should be at this stage .

The fourth stage ： From project to product

From project to product , It's easy to think , It's hard to do . To do the project, we need to listen more to the needs of users , But making products pays more attention to thinking , Thinking about users' pain points and product positioning is far more important than listening to users' statements . From the perspective of project cycle , When making a project, focus on the process of getting requirements and realizing delivery , But making products requires more energy to be spent on product definition 、 Design , And long-term product maintenance . Be a product programmer , We must communicate with customers , You must maintain your own software , Get feedback from users and the market , Only in this way can we realize what functions are urgently needed , How to put technology 、 Combine business with the realization of actual products .

The fifth stage ： Witnesses of product growth

Maybe few people can participate in starting from scratch , After creativity 、 The process from market analysis to product design , A lot of time will be spent on product exploratory work before deciding what to do . Maybe a lot of product prototypes will be made , Maybe some versions and functions are A/B The test was abandoned , Some products disappeared before they spread , Or soon die in the hands of plagiarism and Shanzhai . The replacement and replacement of products are always painstaking , And the visible part is often so simple , But who knows how tortuous its history is ？

The articles are all original without special indication , It shall not be used for any commercial purpose without permission , Please keep the integrity of reprint and indicate the source link 《 Four fire's nagging 》

×Scan to share with WeChat