Summary----Personal blog assignments

I. Summary of software engineering m1/m2

M1

　　M1 is the beginning of our project, that is, the project from scratch, but also the knowledge of our project from the beginning of the learning phase. As far as I'm concerned, I've never written JavaScript code to a more skilled implementation of the various functions required for our project, and I think I've learned a lot more, at least from the code level, that I didn't have as much code as the M1 stage. I think that writing code is like writing math problems, practice more, sometimes although they do not feel, but in fact there will always be a harvest, like a book read times, its meaning from the same. In the M1 phase of my work is probably like this, first of all, a simple study of HTML, for later write JS to do the basis. So the first two weeks is in the "Blind Painting Interface", and finally drew a few ugly pages, and then with some simple features. Although the last few pages are useless, but it seems that two weeks of their own attempt is not futile, their own hand-drawn HTML for my future, such as Dom operation and other related to page interaction JS Implementation laid the foundation. If I write JS directly, perhaps some of the functions can be implemented, but if you do not get the elements in the page, those that need to interact with the function will not be implemented. So with the foundation of the first two weeks, the front-end of the third perimeter is progressing significantly faster. And this time back end of a lot of API has already been provided, because the back end that a few people write very fast, so we can write a function, test a function, a function to complete after the next, when encountering problems quickly and back-end communication, such a one of the implementation. There is a round of reply the day before, the method of sending text messages has not been clear, our PM has been to get 4 o'clock in the morning more in the group sent a message, SMS method finally explored clearly, then he sent a tutorial how to achieve. And, at this time, I and a front-end teammate did not sleep, just a front end of a back end, the next morning to the text message this feature, the next day when the display will also be successful to send SMS features to show out. In general, the M1 phase is a no-no stage, I learned a lot of things, and let me have a feeling in the team.

M2

M2 Stage Although nominally is one months, but the actual high-strength code codes of time probably also more than two weeks, that is, just database, mathematical modeling, compiling all the time for the big homework to formally start, the first few weeks has been the design and learning stage, no how and not so much time to write code. At first, I wanted to refactor the front-end code, so I cut the vue.js in the first week, and it didn't look particularly difficult, but it was just about to start writing. Lying trough, how other subjects so much homework, how can write the end! Therefore, we in the first week after the group will decide whether or not to refactor, or on the original basis to achieve more features, and we M1 when the main implementation of the Community backstage interface, and did not realize the student member's personal interface, so the focus of M2 shifted to achieve more functions above, At the same time continue to use the Sementic-ui painting a few and similar to the original style of the page, the implementation of community management, application management, the station letter and other functions. Now think about it, those days really is dying, four consecutive days of the night, every day is bright day to sleep, and then too lazy to eat, too lazy to take takeout, so one day to eat a meal, the body of the injury is certainly relatively large, but really no way, although has been postponed once, but the workload is too big. And, those days are compiled to test those days, so I also have to draw time to compile, I did not test before. So those days do not take time to write compilation is not possible, I do not want to write this branch of the branch, that is really too hard to force. So M2 summed up a sentence is that ultra-high-strength to die. Until now the rest of the time has not been adjusted to come, three or four o'clock night is not sleepy, the alarm clock in the morning more than 10 to wake up. And M2 stage also a little episode, originally we want to change the first stage of code management mode, so the second round with GitHub, although the original has been used a few times, but not so systematic use. At first, I wrote a front-end code management scenario:

(first to clarify the front-end code modification process, the front end is not like the backend can be modified directly on the server, the front-end is usually on their own computer and then uploaded after the server for debugging. Because directly to the putty to modify the HTML and JS code is really inconvenient (at least I think, vi is not very skilled), so we used to generally use the following process:

Local modifications, upload to server, debug->{local modifications, upload to server, debug->}-> upload to server final release path

Now that you've added GitHub to manage your code, the process has changed.

Local modifications, upload to server, debug->{local modifications, upload to server, debug->}-> upload to github-> server pull from GitHub to get the latest version)

I reckoned this process is certainly not very formal, but at last it is guaranteed to ensure that every time the server pull, the remote is a full project that can be used for publishing. I myself think this is not too much trouble, but, the front-end to later is also anxious, did not follow this, directly changed to the server PORT80, there is a page I wrote a night function are realized, and then a look how all did not, the original is let others to cover off. At that time, my body was empty, so a fright, really can't stand it.

Ii. Analysis of reading assignments and related issues in the law of construction

Problem Link: http://www.cnblogs.com/fusluv/p/4830967.html

1. In the book without analysis of the blind optimization is not advisable, although our project does not use too much optimization, I am also encountered in the DOM Operation simplification optimization, but I still feel that should be a long time to consider what changes may be made later, dragged to the project size is relatively large when there is no way to modify, For example, we M2 the first weekly hours Vue.js is the time, this thing really is good, write up not trouble, want to completely reconstruct really is not that energy. So at the beginning, we should plan well, think more about the construction.

2. The problem of market demand, I did not do a lot of understanding, but at least I feel that the need to feel that the demand is very practical, do not think that their own writing code is not appropriate to the needs of the line, in that case, write also no motivation.

3. Group personnel level, I in 7 people inside the level should be the lowest, the result is also the lowest (so I feel this semester like a nightmare, those strong or comfortable). , but I am the head of the front, probably because I spend more time, it would not be anything, and then the front end of the problem of another few people will come to ask me. Now think, growth is still relatively big, originally this semester soft work is want to hug thigh, thigh did not hug, but is tired become a dog.

4. Innovators are not pioneers, and sometimes it is true that people who start with ideas often do not give practical action, and finally others realize the idea of the person. Real life is like this, and do not still have those creative companies, is responsible for thinking creative, not responsible for the realization, the Church apprentice starved Master I think not particularly possible, master always has a person's place, apprentice also always have their own good aspect, after all, this it market is too big, all share also can not finish, At least for now, I don't know anymore.

5. "How can business and scientific values be balanced in the interest of money or the pursuit of a particularly ingenious process", I first stick to this problem, because the problem was a little too big, and now I can not answer. Money must be there, no money to eat soil wow, but, people can not be so little pursuit, sometimes always a bit ideal is not. Also, I would like to do something that is not very relevant to the industry, to develop some other hobbies. Life doesn't have to be more brilliant, but it has to be a bit of a point.

Third, the paper reading homework and experience

In general, the same understanding as before. It is not so much the same as the experience of more than two iterations of development, more profound.

First is the silver bullet problem, I still think the silver bullet search is necessary, although not deliberately looking for, but always to continue to learn, continue to find more convenient way. But also must pay attention to the foundation, the building without foundation is impossible to build.

Big mud ball problem, this problem appears in our development very serious, at that time those who can cause the big mud ball reason basically all met, really is thought of also did not avoid ... In the future to pay attention to it ...

The rest of the questions, experience no change, no personal experience, do not repeat the

Four, 6 Stages of learning experience:

Requirements: Learning the methods of investigating user needs, and in the detailed design of requirements, we also learned the NABC method.

Design: Bottom up and top down two large types, we are mainly from the top down this time, continuous refinement function. And in the API design when the front end of the side to discuss and evaluate the implementation of the difficulty.

Realization: This has nothing to refine the experience, feel that this is an accumulation of knowledge released the main stage. Of course, must be in demand analysis is correct, design reasonable Foundation

Testing: Testing methods such as unit testing, stress testing, compatibility testing of different platforms

Release: Be sure to have a release manual, let others actively explore your project is not very realistic. And after the release, there's a summary post-mortem analysis.

Maintenance: Constantly discovering and fixing bugs to improve the user experience.

V. Suggestions for this course:

First of all, we must affirm the significance of this course, but perhaps because it is still in the exploratory stage, so I still take a student's point of view to talk about the lack of this course.

1. Time planning issues, time is still a bit unreasonable, especially in this semester, in the next semester or senior may be better, just this semester is all the classes lesson. True, if really can put our first design all realized, and then more than one more time can not be finished, and finally some features did not realize or a little regret it.

2. The question of assessment is not that there is any problem in the way of examination, that is, there are some loopholes in supervision. Although students do not want to look like a child, but for example, pair programming is really a person hug another person's thigh, is exactly what a person does and how to find. The same is true for team work. Although I also want to hug a leg at the beginning, but I am still very fortunate that I did not embrace, instead of learning a lot of things.

3. The problem of stage display always occupies the course time. Although it may be the teacher to arrange the course time, but often is the beginning of a class, showing that each team report, a report is more than one class, the course will become a bunch of PM report class ... Not that I don't want to learn the strengths of other teams, I'm really interested in listening to other groups reporting that long.

Finally, I wish this class more and more good, thanks to the class of the explorers, I hope that students can learn more things, this semester I am also painted a complete stop.

Summary----Personal blog assignments