Aite Tribe Story Collection (26): Full Stack Siege Lion's Sunflower Treasure Book

[51CTO.com original article] Xiao Xingxing, who has dabbled in mobile, front-end, and back-end, is not proficient in all kinds of skills, but is also familiar with them and can use them freely. Now he looks back on his IT pit and shares his growth experience with everyone. From JS to Java to PHP, the full-stack engineer is now online.

[[200696]]

Little Star PHP

Xiao Xingxing's entry language is AS, yes, the Flash scripting language. He broke into this vast IT world from a side door, so he learned JavaScript, HTML, CSS, C/C++, Java, PHP and other languages. Flash pursues beauty and harmony, it always gives people a kind of aesthetic enjoyment, so this habit of "loving beauty" has been maintained, so that later on, when learning other languages, he would be entangled in various formats, and slowly developed the ability of cleanliness. Yes, it is cleanliness!

Budding Awareness

The first time I learned ActionScript was to satisfy the response of an interactive button in a Flash scene. In order to add the onclick event, Xiao Xingxing remembered that it took him half a year (I laugh at myself, it was so hard back then!). When he saw the prompt message appear, he was so excited that he almost jumped up. It was so hard-won. From then on, he realized the concept of "object", that is, a real object, or Object.

With objects, many repeated layer elements can be merged together, and many scene operations can be easily handled. The specific operation method is to abstract various components on the timeline and organize them into various scenes through components. The biggest advantage of abstraction is that it can be reused, reducing the coupling between scene contexts, which also makes the work more maintainable.

Growing through self-struggle-discovering flaws

After I got to know JavaScript, I found that its syntax was surprisingly similar to AS. It was not surprising. Later, I learned that their cores were both ecmascript. Anyway, it took almost no effort to get started with JavaScript. After using AS to take over half of the commonly used JS, I found that some functions were redundant or not neat enough. For example:

 var hasContent; 
 
 if (arr.length > 0){ 
 
 hasContent = true ; 
 
 } else { 
 
 hasContent = false ; 
 
 }

In fact, it can be handled with a very simple sentence: var hasContent = arr.length > 0; Of course, if you want to be more rigorous, there is a time bomb here, that is, when the variable arr is null, an error will be reported and the process cannot continue, so the improvement should be:

var hasContent = arr != null && arr.length > 0;

The above is a very simple variable judgment and assignment, which can be written very concisely. Another thing is the naming of variables and methods. Some people like camel case naming, and some people like lowercase letters with underscores. These are all fine. The unified writing method makes people feel comfortable, but often some look crazy. For example, the above example uses their writing method:

 var a; 
 
 if (b.length > 0){ 
 
 a = true ; 
 
 } else { 
 
 a = false ; 
 
 }

The readability of this kind of code is very poor. Every line is almost guessed. The above one is relatively easy to guess. If the length is a little longer, the reader will feel like vomiting blood.

Therefore, from the perspective of coding, whether a piece of code or a program is a horse or a mule can be clearly seen by whether it is neat and easy to understand. Of course, robustness is also important, because it can't crash while running. Therefore, as long as third-party code is accepted into Xiaoxingxing's work, he will modify the code to make it less incompatible with his original logic. Of course, the author is still signed as the original author. In this way, it can be said that he has trained his own pair of sharp eyes. He can see at a glance where there may be problems in other people's codes. This can be regarded as the result of self-entanglement. Writing good code is convenient for yourself and others.

Zeroing and Recording

After crossing the first threshold, the coding journey will be much smoother, and basically you don't have to worry about things at the syntax level. Instead, you should think more about how to organize the code structure to complete a function, and how to do it more efficiently and robustly. For example, encapsulation, sub-packaging, and abstract public interfaces all require sufficient coding experience as support. As for Xiao Xingxing, because he usually pursues perfection, he will try all kinds of situations that he thinks are good, so he has the following work, which can be regarded as a trace of his personal work in Java.

Toolkits accumulated from various Java projects

Yes, at this time, the pursuit of cross-platform, that is, want to implement everything that Android has on PC, or want to implement everything that PC has on Android, this is entangled and brain-burning! The advantage is that when encountering some compatibility issues in other coding work, you will consider them more thoroughly.

There is something about image recognition here. It seems that it was because of a dependency library version problem (it was upgraded silently). The well-made code just couldn't be compiled. After various attempts, there was no progress. When he was at a loss, Baidu, which was used to reading a lot, gave him a message in a very inconspicuous corner: "The latest released version of xxxxx is v2.4.0". He was so disappointed that he rekindled his hope and started to work immediately. Sure enough, after upgrading the dependency library, everything returned to normal. This was a huge pit, absolutely! It was midnight at that time. In order to remember it, I decided to record this pit, so I met ddJava (translated as: Dingding Java), the owner of the forum was "Gorilla". At that time, this was a brand new forum, and I almost picked up a sofa. Haha, thanks to the gorilla!

Posting on the forum to record problems is also a process of reviewing. During this period, you may find new problems and new solutions to the problems. To some extent, this is also a learning process. After solving the problem, looking back, you may find a better solution!

The compilation problem was solved, but another problem arose. The matching algorithm at the time was rather complicated and could only match the specified area. The specified area is to determine the coordinates, and the method is to pass the coordinates together when matching the parameters. Xiao Xingxing thought so and did so, debugging in the middle of the night. When it was finished, he mentioned this to a big shot in the company, and the other party said: Why don’t you put your coordinates in the image file name! Isn’t it more convenient to parse the file name directly when matching? Xiao Xingxing suddenly realized that the masters are indeed different. They can often grasp the key points of the problem and can handle the problem very sharply. This is another way to learn, to communicate with the masters, share what you know, and let the masters point out areas for improvement and optimization.

Thinking in reverse

When you are already familiar with the functional code, you will find that the small problems in front of you are not problems, but the big problems formed by countless small problems together are difficult to overcome. This is another hurdle in the growth process. When you have mastered the language in terms of skills, the remaining issues to consider are system performance and business logic, that is, how to perfectly cooperate with your own code to complete a given business without affecting the maintainability, stability and operating efficiency of the system. Maybe method one is feasible, method two is also OK, and method three is also OK. At this time, you need to rise to a higher level in your thinking, jump out, look down from the top level, and guide your coding based on the needs.

For example, the product needs to add a search option to a list, and this option involves another or several large tables with tens of millions of data (MySQL, yes, it is still very popular at present). From a grammatical level, this problem is very simple. The method is to directly join the tables and add new filtering conditions in the conditions. This method can meet the needs of the product, but the problem is that people who use the system will go crazy because of the slowness! The problem is that large tables are joined and queried, which consumes database performance. Users need this function but they will not accept the slowness caused by it, so method 1 is not feasible.

Is there a second method? Yes, there is definitely one! Since cross-table retrieval affects efficiency, don't let it cross tables. The method is to first filter the target condition in the driver table where it is located to obtain the target value, and then use this intermediate value to filter the query in the main table. I believe this method is not difficult, but when the amount of data increases, this method will definitely be several times faster than directly joining tables.

Method three? Yes, think from a higher level. The most thorough approach is to start from the design of the relational table and avoid large table join queries as much as possible from the root (well, this has not been actually tried, but it is feasible, and I have seen some hardcore tasks do this). In addition, you can also use the powerful computing power of the server to read the target data into the memory and perform conditional search in the memory. I believe this approach will exponentially improve the performance of multiple large table searches.

【Written at the end】

Entering the IT industry, I encountered countless pitfalls, but my "serious" spirit allowed me to overcome each barrier one by one, and I also developed from a novice to a full-stack developer. Whether it was mobile, PC, front-end, back-end, development, or operation and maintenance, I persisted, studied, and tried my best to find the best solution for each task. Think more, communicate more, and you will find that you are not far from the full stack!

If you are also willing to share your story, please join the 51CTO developer QQ exchange group 542270018 and contact the group owner. We look forward to your wonderful story!

[51CTO original article, please indicate the original author and source as 51CTO.com when reprinting on partner sites]