Once a week 01& the beginning

The account has been applied for some time, the origin of many online query technical questions of the answer, plus the circle has this ethos, so there are these, this is where all the beginning.

First I found that the technical article is not so easy, at least I do not want to grab a piece of code to throw up, at least a bit of meaning, to the blank editor is Evans Fountain, can be dragged from scratch to the state of the claw. Think, at least a week to write an essay, or a week should be a little harvest, essays may not have to form a complete code logic, as a record and witness, in the future also have a role, said.

First, a further understanding of the use of the framework, familiar with a framework, first to understand the basic file structure, what is where, and the naming of the specification. They all help users to quickly locate the files they need, to help them understand their role, and to integrate into the big frame when they do their own work, without messing around and stepping deeper. Speaking of which, the core of PHP files, still lack a clear definition, the first to focus on what? This can then be summed up separately.

Another point is that the preparation, that is, what to do before the specific code, ax. For a team, the unified standard is to pay attention to, the beginning I get the argument is: development tools casually, the environment casually, see for themselves first, then sent the task. For the newcomer, it would be a disaster, and all that is now dug with the pretext of fooling, in a tightly-knit world, is to be filled at a later cost. I think even an old ape, when entering a new team, should try to use a unified tool, the implementation of a unified standard of work, the standard to what extent, debatable, the current environment is not reference, need time to practice and more knowledge, and if it is new, everything is fresh, then a consistent tool, A certain standard, will greatly accelerate his integration speed and the cost of getting help down, everyone can, or should have their own way. But the truth is that most of the work is repetitive. This is not necessary, in the material level is not sentimental, not to mention for the company, the pursuit of work efficiency, wild way is not worthy of praise, differences is the king, so, please give new packaging environment, configuration, some standards, a little advice.

Said a bunch of specific technology has nothing to do with, the following code is always not feel right. So, the current understanding of the growth of personal ability, programming aspects:

1 Consider what to do, how to do, and then to do, as time goes on, this proportion should gradually increase, eventually become reasonable, and will show its role.

2 to the existing old code to try to understand, the code you write several times to explore, try to modify, can deepen the understanding of the work, improve their own code is a visual progress.

3 from the beginning to develop good code writing specifications, logic norms, which is a long-term career and rich content, recently looked at some predecessors, should be alone in summing up an article.

4 Keep learning attitude, actively invest in yourself, actively learn useful new technology, grasp the degree.

Once a week 01& the beginning