October Study Summary: Choose the right framework for rapid development

Objective:

September did not write a study summary, September things a bit more, usually learning time is too little, the work is just repeatedly made some wheels, nothing can be recorded, there is no summary, the direct leap Forward, the October summary, if the October does not summarize, that is the Great leap forward to November, hahaha.

First, select the appropriate framework for rapid development

Mission Brief:

October took a task, do a baby style contest, parameter personnel upload photos, pull friends and family to vote, according to the rankings have various awards.

Process Description:

I am responsible for development as the master, a front-end to do HTML assist me. Look at the design, we two people, evaluated the project, about a week can be completed. The idea is always good, the reality is too skinny.

I want the front end to be based on a framework for development (such as bootstrap or other can be in the IE7 good layout, etc.), the front-end people most always choose their own pure handwriting, do not rely on any framework, OK, then start.

Back-End function is not much, is the image upload, logic processing, several data tables established, because it is a one-time function, so the backend involved in the specification is not strictly required. The backend is finished on schedule, and the rest is docking with the front-end HTML (because we didn't do a read-write separation, well, we don't have this one at all). Because it is a relatively urgent project, the front end has not stopped, write a page will give me one. But I got the page, data assembly, under IE, a variety of compatibility issues burst, testers gave a lot of compatibility issues (page +js), no, time and urgency, I began to participate in the revision of compatibility issues among the ranks .... In this way, in the compatibility issue, we finally spent 2 weeks to complete these tasks.

Summarize:

In fact, like some of the features, I am inclined to use the front-end framework for development, one is because I am not a professional front-end, write native JS for me, the basic use of jquery, the second is that I started from the front end to write to the backend, there are some experience in the front end.

The framework is naturally constrained and has advantages and disadvantages. But it is right to choose the right method at the right time, after all, a good framework is contributed by a lot of people, unless the framework has not reached our requirements, then, it can not be written.

It's not just the front-end framework, it's the PHP framework. I hold that view. Now that I can't write a better framework, I learn to use good frameworks like Yii, Laravel, etc.

I have seen in the interview some people think very nb, to me bragging about the framework they wrote for the company, how, when you read his source and function, you will find that SB still quite a lot of.

Second, bring the good things.

We are now using a framework that is purchased by someone else's company development Framework, not written by themselves, of course, we currently do not have the ability to write one. But this framework is a lot of problems, there are a variety of problems, and many features are not perfect, so we can only tinker.

It's just tinkering, and it's not going to make up for what's not enough. For example, a very obvious thing, a lot of customers complained about our form after the submission, prompt error, after returning the form, fill out the data is not. That's not going to work, but what? No one is going to add a feature to this.

Before I learned laravel, I saw that there was a term called flash flash memory, that is, the data is saved until the next use. And Laravel is also used in form form, so according to gourd painting scoop, also simply wrote a, used in the framework, to compensate for this deficiency, although imperfect, at least can solve some problems.

Git address: Https://git.oschina.net/ken.yang/shopnc_flash

In fact, we are complaining about a bad thing, but you have to use it again, why don't you think how to make it better?

Three, digging their own pits, teammates to help you dig, and then bury themselves

Here I am not complaining and spit groove, just want to put the heart of things to say, recently done something a little touch. Because I have done such things before, so now programming very attention to these, do not bury too many pits, not only pit others, but also pit themselves.

Our projects are guided by results (which, of course, are related to the company's level and look less on the right track). Often meet today to ask for the function of tomorrow's people, in this case, can only be how simple how to do ...

Guidance is too many reasons, can not blame others, their own code when more attention, more efforts to strive to do a good yard animal.

Four, try to write a second kill device

This should be the title of the party, is written for a website, in fact, can not be analyzed page elements, js,form form submission method, verification, etc., but there is a little gain, know their website should consider how to prevent these problems.

In the process also found that chrome is very nice, because you can edit the page JS, and Firefox and IE can't edit js, so you can directly handle the above page JS operation.

Summarize:

New to a manager, big ideas speak a big push, no one to you say concrete how to do, task take down or to oneself slowly to grope.

But to learn some new ideas, we need to comb a good summary.

October Study Summary: Choose the right framework for rapid development