Aiti Tribe Stories (24): Rooted in the technology circle, with a strong sense of belonging

Aiti Tribe Stories (24): Rooted in the technology circle, with a strong sense of belonging

[51CTO.com original article] The protagonist of this issue, Xiao Xingxing, lives in Guangzhou, a very vibrant city. He had a near-death experience a few years ago, and he actually started his coding life from Flash animation, and accidentally entered the IT tribe. In the following years, he worked on VB desktop programs, complex C/C++ algorithms, wrote a huge Java portal, and played with hybrid programming, namely AppCan. Now he is proficient in PHP, the world's most popular language (^_ ^), haha, that's it. Looking back on his experiences during this period, he is most deeply involved in Java language and Android-related things, which can be said to be his best programming; Xiao Xingxing has been involved in PHP for the longest time, after all, the current system is built with it; and the most interesting and unforgettable time is the time when he used AppCan!

[[198091]]

Little Star·PHP Development

Programming awareness bud

After Xiao Xingxing left his last job, he worked on outsourcing projects with his team for a while, a large part of which was WeChat applications. As a novice, he was particularly entangled with HTML5 and CSS3. It can be said that he lost a lot of weight after several projects (well, he was already a big skinny guy), and it was very brain-burning. However, he was familiar with the various adaptations and compatibilities that need to be considered in mobile app development, asynchronous requests are a good way to improve interactions, and what operations should be done for data security during interactions, etc., and he gained a lot. Later, when Xiao Xingxing was interviewing for a development job, he was asked a question about the trend of mobile terminal development. He believed that "cross-platform app construction based on H5 will be a trend." At that time, he had not learned any information about Hybrid App (well, information lag or lack of cognition is very terrible, but after all the tossing of the project, he still had this awareness), but he still appreciated his "foresight"!

App Custom Component Development Ideas

When the outsourcing project was going well, the person in charge suddenly threw a system over. It was a very "huge" system. At least in the eyes of his team at that time, it was very complicated (it took three days to modify a menu bar option. Yes, it was very scary)! Then, Xiao Xingxing was very honored to take over the responsibility of this project. As a result, he received calls on New Year's Eve and New Year's Day to urge progress. He had a very special Spring Festival in 2015. Since then, Xiao Xingxing has made a grudge against that system. Not only was it complicated, but the key was that there were so many bugs that he couldn't understand and accept. I didn't expect that the tears were still to come. After he took over that "cute" system, he worked directly until now. Yes, now!

Although the system was complicated, it could bring revenue to Xiao Xingxing's team after all, and it also needed a mobile terminal. Worried that development resources were very scarce and he could not take the conventional path, he looked for various hybrid development platforms and tools, and finally his team chose AppCan.

Because of his experience in H5, he took on the task of building an App based on AppCan. The preparation work included translating various official website documents, trying various IDEs, and joining various official communication groups. Anyway, he just started working. It was July at that time, Guangzhou was hot, and Xiao Xingxing was also working in full swing. Since he had spent time studying the official documents before, he did not encounter too many difficulties when building the App, and he could basically digest it by himself. The difficulty lies in the fact that his own App requires some highly customizable components, such as sliders, progress bars, image cropping, and line charts. These all have a unified foreground and background, unified fonts and line styles. It is impossible to use ready-made ones, so he has to make his own. Let's start with the simple one. The first one is a progress bar, as follows:

The idea at that time was to decompose it into text prompt, foreground, background and status on the right. Each part was implemented with div, and he also wanted to achieve reuse. When needed, a new instance was created and some parameters were set to produce such a thing. It was done right away. The idea was simple and the actual practice was also very simple. It was indeed:

1) This is the component target location:

2) Import custom CSS and JS:

3) Instantiation:

The usage is like this, well, it's quite elegant. Here is the extension entry of the style, the definition of the minimum value, and the definition of the foreground and background.

The specific implementation idea is: the background has a fixed width and height, the foreground is the same height as the background, and is aligned with the background on the left. The foreground is set with a highlight color, and the width is specified by the progress. The width ratio of the foreground in the background is determined according to the progress ratio. This realizes the progress display. In addition, the display text needs to set a larger z-index attribute, and is centered above the background. The principle of the rightmost state is the same, but it is centered on the right. Attached is the implementation code. Click here to download the extra directory (well, in the form of files, there are too many codes to post here. There are also several other components, all built based on AppCan 3.2 version. As for whether the current new version is applicable, Xiao Xingxing has not verified it).

Finding a sense of belonging in the technology circle

This is Xiao Xingxing's first component encapsulation in H5, and he feels a great sense of accomplishment. It seems that someone in a hybrid development group asked a similar question about the progress bar component, so he was happy to share his "research". Being able to help others is also a reflection of his own value. Sharing is also a very happy thing. In the following time, he shared several components he encapsulated with everyone. Gradually, he became an active member in the group. One day, on a whim, influenced by everyone (everyone is very cute), he changed his note to "Guangzhou-Xiao Xingxing", which is Xiao Xingxing known by many people in the technical exchange group.

During the days of working in the group, he met many coders. To be honest, this is a very happy team. On a certain day of a certain month, the official representative of the technical group invited him to join the management team because he was more active. After asking specific questions, he was successfully shortlisted. From then on, Xiao Xingxing took root in the technical exchange group. More importantly, because of this team, he also received a special gift.

From the perspective of vitality, the technical exchange group is a team that can be trusted. Apart from the technical direction it represents, everyone from different regions, companies and industries gathers here to discuss, solve problems and propose improvement suggestions. This represents tenacious vitality. If it is alive, the technology it represents is alive. In the IT industry, maintaining a vibrant team gives you the reason and motivation to keep growing bigger and stronger!

Looking back on the pitfalls that Little Star has encountered, it can be summarized into four points: decomposition, summary, recording and sharing .

1. Decomposition. The problems encountered during the development process are difficult or easy. When you encounter a difficult problem, you need to decompose it. For example, a complex UI component can be decomposed into multiple simple div blocks, and a complex function can be decomposed into multiple simple functions, that is, simplifying the complex. Doing this is an improvement in your ability.

2. Summarize. In the process of solving problems, it is appropriate to look back and make some summaries. This can not only consolidate your ideas for solving problems, but also find inappropriate or insufficient ways of dealing with problems, so as to summarize better ways of dealing with or improving them. This is also a process of improving your ability.

3. Recording. Recording has another benefit. Detailed and organized records are also a good reference for others to deal with the same or similar problems. This is sharing. From this perspective, how to better share your own things and minimize the questions of others is another improvement in functional planning and information organization.

4. Sharing is the most important thing. Maybe you need a "little star" in your life. There will always be disappointments in the process of growing up. Having a spiritual pillar, or a value standard, will prevent you from being discouraged in adversity and prevent you from being carried away by success in prosperity. We all understand this!

Life is meaningful only when it has its ups and downs. For a few months, Xiao Xingxing had a hard time, and so did his team. It was because of the presence of these people in the technical group that he had the spiritual support to get through it. The leader of the Xiao Xingxing team also took the pill of reassurance because of the persistence of him and his colleagues, and led the team through the difficult period. Thank you!

Xiao Xingxing is a little star who loves to share. He will organize and package the demos that he has written well or feels good, so that friends in need can use them directly. This is one reason. Another reason is that in the process of organizing, he can also find those factors that are not harmonious, such as whether the introduced resource files are concise enough, whether the instantiation process is convenient enough, whether the parameters are clear enough, and whether the documentation is straightforward and simple enough. These are what users need, and they are also a direction for him to do similar encapsulation. This is a good way to improve his thinking and coding skills. After completing a project, summarizing and recording it is a valuable thing for the growth of oneself and others.

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]

<<:  Modern front-end development technology stack

>>:  Deep understanding of pathfinding algorithms in games

Recommend

5 steps to early warning and user recall

In user operations , in addition to attracting ne...

How much does it cost to customize a watch mini program in Handan?

How much does it cost to customize the Handan wat...

Is the information flow product-centric or user-centric?

In life, the things we come into contact with the...

Magical device or hidden danger? Clearing up the mystery surrounding humidifiers

Whether it is central heating in the north or ele...

Kuaishou Advertising Creative Guide for 2019!

Driven by multiple forces including users, platfo...

How to monetize your Tik Tok video editing account

When we browse Douyin daily, we can see various m...

Windows 10: A return to tradition

Windows 10 Technical Preview has been released fo...

How to attract new users to Meituan, Ele.me and other apps

Some people lament that life service platforms su...

How deep learning is bringing personalization to the internet

[[195601]] Deep learning is a subset of machine l...