1st personal work: reading and preparation work

This work belongs courses course
Where the job requires Work requirements
My aim in this course is 1. Create a project to learn the basic tools and basic methods
2. consolidate learned programming languages
3. improve their ability to code written by the actual operation
4. Development of an own small products
In particular aspects of the job which helped me achieve goals 1. theoretical knowledge of materials
2. Build projects and group work
3. Individual project build
4. Learning to build project management tools

First, establish a blog and introduce yourself

 1. Personal blog: https://www.cnblogs.com/Mr-Chopper/
 2. introduce myself: I am a junior student, not in class most of the time in the bedroom house, though, I still regularly to do sports. Are setting their own goals, do a little planning for his next life. Confused, after all, it is a terrible thing.

Second, reading and thinking

  1. Recall Imagine when you are entering the university in your professional

  • How did you make choices in your professional decisions?
      Turn professional to be believed, the original intention is not only just like the original professional
  • Do you think the past (two) years of exposure to the course meet your expectations of yourself where professional, and why?
      In line with their expectations; two semesters of study, subjects learned professional involved in a wide range, can learn a lot of information.
  • Do you think a professional in your field that you like it, it is an area you're good at it?
      This is more to learn about the professional interest is the best teacher. Thus, far from good.
  • In the future you will choose to engage with your professional work related to it? If you want to go is a given city, company and job, if no reason is given
      employment preference is certainly relevant professional work, but for me, there is not a long-term plan posts (more than 5 years). Place to go to work: Chengdu, Wuhan. Now the company did not know what.
    2. Before the control of people walked the streets and describe future development, and now you
  • Feel you already have professional knowledge, skills, abilities, what? The amount of code has been written is how much? Describe the most complex projects do you
      have professional knowledge is the basic professional knowledge, skills is to install the software, it seems to have the ability to not show it; the amount of code written probably about 1000 lines; have not done the project
  • From becoming a qualified graduates in the professional knowledge, skills, abilities but also the gap between what?
      Professional knowledge and understanding of the basic principles; unskilled operation of specialized software; geospatial database development and the process of developing an understanding of the algorithm.
    3. The current selection is a crossroads in life, something was working, public test, go abroad, there are different options at different junior endeavors. And each path whether or postgraduate work, there are many different branches.
  • Control over before you read people's experience, what is your choice?
      Work, find a stable job done 3-5 years.
  • In this option, you think What are the advantages, what are your weaknesses compared to other classmates?
      I have not thought about it, but I hope not too much risk.
  • For your choice, you give yourself a junior planning arrangements set what is?
      Study hard expertise. Master a programming language.
  • For you to achieve your dreams have done or plan to do what kind of preparation?
      From the first to change their habits. Did not plan too far, after all, the plan is to keep up with changes.

    Third, there is mention of quality problems

     Q1: Chapter II mentioned unit tests must be written by the person (Author) most familiar with the code , though the code is the author most people understand the code, but the code for authors thinking when writing code should be constant, but can not out of the original mode of thinking, so I think, we need an experienced person when unit testing assisted.
     Q2. Chapter III software engineer career development software engineers should be some work ethic and attitude should be?
     Q3. Chapter Nine mentioned leadership ---- efficient team discussed this semester we have had to do a project team, we all want to do it well, so the project implementation will need to we can discuss how to efficiently get on?
     . Q4 Chapter 12, "User Experience": a good user experience, of course everyone wants, and if it has the quality of conflict, how do? To sacrifice quality to the user experience, the user can accept it? Quality is an important factor in determining software revenues, but the user experience is also very important, the software itself is facing a lot of users, so the trade-off between the two as and choose?
     Q5 Chapter XIV, "quality assurance": software development process has three main features: "good", "fast", "cheap." Popular understanding is that "software meets the functionality, cost, time three demands of stakeholders," the high cost of the software development process, how to do it at a lower cost, to make the software meet the functional requirements, but also contractual time limit?

    Fourth, understand and investigate the source code version management tools

    advantage Shortcoming
    Git 1. Free and open source.
    2. A process for any small or large projects quickly and efficiently.
    3.Git support branch function (branch). If you want to develop a new product feature, you can set up a branch, make changes to this branch, and thus will not affect the code on the main branch.
    4. Git can take to make backup system, or sync documents two machines, it is convenient.
    5. Support offline work. Local submission can be submitted later to the server, and do not interact with centralized code management server. Only the finished version only need to submit to a centralized code management center server.
    6. Git are submitted atoms, and the entire range of items, rather than the CVS is the same for each file.
    7.Git each working tree contains a complete history of the project has a warehouse.
    8. A simple initialization. For just write two lines of code into the code management tools will of the people, the very appropriate.
    1. Study the big cost. Excessive progressive approach very long, requires a lot of time.
    2.Git repository requires frequent manual maintenance.
    Trac 1.Trac make a SCM configuration management platform, which means it has good scalability
    2.Trac permissions system is relatively complete design
    3. very flexible and can be customized arbitrary, and can be integrated TortoiseSVN.
    1. does not support multiple projects,
    2 requirements and defects are not separated,
    3. wiki instead of Word and other tools to write documentation for product planning for the threshold is too high, rarely core function, do not install the plug-in basically can not use.
    Microsoft TFS 1. Mandate version can on demand, project progress glance, for a small team, more than a Gantt chart with
    an integrated 2 project management, version control, BUG tracking, can effectively achieve SCRUM
    3. seamlessly with VS join
    1. The whole system is implemented using asp, accessed with a browser rather slow (do not know if server performance is too low or my personal computer configuration is too low)
    2. Access from IE, fill in the various development, test records, is very slow, so the feeling is better mantis BT php based so easily and quickly
    3.XP can not access the system, you had to be 64-bit. So the computer's overall performance dragged down
    Mercurial 1. Lower barrier of entry. Overall, hg need to know a lot less command than git.
    2. can be a key to fully restore historical versions of a particular section.
    3. Good package. Compared git, hg rarely reveal details in some implementations.
    4. svn take care of the migration of users. hg many commands are migrated from svn command, in fact, the goal is to make it easier for users to accept svn. This makes the svn command team have become accustomed to almost zero cost to switch to hg.
    More 5.hg of pull when you can let you avoid creating branches. hg like Apple system, git like Linux, the former is easier to use and easier to use on commonly used commands, which is on the more powerful and more flexible.
    6.hg repository does not require maintenance.
    Branch management is not flexible. Mercurial and Git's branch management is not very convenient compared.

Guess you like

Origin www.cnblogs.com/Mr-Chopper/p/11505913.html