This article briefly describes my own experience of software development and some ideas, and simply share some of their own experience.
I. Views on development experience:1, the accumulation of experience is very important. This is because it takes the most valuable time + project opportunity and practice to gain, whether it is success or failure of experience, must be accumulated. These experiences will make us more successful and do the next thing. 2, it is noteworthy that experience can not be mechanically, can not let experience imprison our thinking, experience also has a certain application scenario, and may lapse over time. Therefore, the experience that summarizes, sometimes also need to examine, rectify and perfect. 3, experience this thing, direct to others, others have not personally experienced, and sometimes, others may not necessarily understand. due to the importance of experience, special here to record some of their own experience in the project,
this is only a beginning, will be based on their own practice to continuously supplement, perfect
second, share the experience:1, fast is slow. Do not in order to catch up with the progress, and ignore the quality of the product, even their own that can not pass. Otherwise, and the tester's repeated interaction, but will make less efficient, and ultimately just the immediate, the progress eventually become slower. 2. Project Time Evaluation Method1) Subdivision and subdivision of work breakdown2) Ask a professional colleague. Your own technology and understanding of the business is not necessarily exhaustive, this time to ask professional people, or specific work directly responsible personLast) Dead brace : Two words, overtime. Project evaluation time, difficult to assess 100% accurate, because, software development, code writing work is difficult to quantify, sometimes there are some potential risks, so the evaluation time can only be as accurate as possible. 3, Agile Project Fixed steps1) Feasibility, impact surface, risk, output (although many times is leader think, but you think more, you also become leader)2) How to do, what to prepare, think about the most likely to hinder the risk of the project is what, think well in time to respond to the method3) Evaluate time, input, and project plan4) Project implementation (from time to time to see if progress is consistent with the plan to see if there are risks and work not previously considered)5) project summary. summarize what places to do better, then use the next project, summarize what place is not good enough to avoid these problems in the next project 4, Technical solutions Choose fixed Steps1) Understand technical requirements2) Compare the industry's existing solutions to see where the pros and cons of different solutions are, and which solutions have the advantages to match their
status and needs. the status quo and needs are important, because the best is not necessarily the most consistent with their own team, and the choice to consider the future development3) Solution Quick Model Check
third, written in the last:This article lists only my short-sighted work experience summary of some of the experience, you are welcome to Daniel, and share their experience
Software development work experience sharing
