Reflections and Prospects of iOS Developers from 2016 to 2018

[[222173]]

Preface

I have been working in iOS development for nearly two years and have made some progress, but there are still many areas where I am lacking. I have thought a lot and learned a lot from the valuable experience of experts in the same field, so I wrote an article about my personal reflections and prospects.

Reflection

quick

As a relatively young development engineer, I am not a computer major. I know that my computer foundation is relatively weak and I am eager to learn. In addition, there are countless articles and books available for learning on the Internet. Sometimes, I am lazy and cannot help but read articles about multithreading, networking, runtime, etc. in one day, creating a false impression for myself (Wow, I have learned a lot of knowledge today). However, this kind of reading is often just a kind of extensive reading. If you read an article easily, you will not be able to appreciate the deep meaning of the article at all, and you will not be able to internalize the knowledge points in it into your own knowledge system. What you learn in this way may be completely forgotten by you the next day. Continuous extensive reading for a long time will not improve your personal skills much.

Fear of difficulties

In the daily development process, you will always encounter more difficult requirements, which is a good opportunity for you to expand your knowledge. But everyone tends to stay in their comfort zone. Especially when I am in a relatively low state, whether psychologically or physically, I will immediately feel a sense of fear, thinking to myself (I will just deal with it carelessly this time, and when I feel better, I will chew this hard bone carefully). Afterwards, I may have thrown the original idea behind and just do nothing. Little did I know that this really missed an opportunity to improve myself. Although this situation only happens occasionally, I still feel ashamed when I think about it.

Lack of long-term planning

Every time a plan is born, it is made on a whim, and it is abandoned after a short time. Reflecting on it, the main problem is that the initial plan sets too heavy a daily task. On days when the development tasks are relatively easy, it is relatively easy to complete. But when the project schedule is tight, it will cause a great burden to oneself, resulting in failure to complete it from time to time, and ultimately leading to the interruption of the plan. This kind of persistence based purely on willpower cannot last long.

Outlook

slow

Slow is fast. Good wine always gets better with age. Knowledge also needs to settle slowly. In the process of learning, slow yourself down. Select high-quality articles and read them carefully. It is enough to read one article a day or even one article a week. I personally think that intensive reading must meet the following requirements:

Read through: Understand the purpose of the entire article and what aspects it is about. Have a certain grasp of the structure of the entire article, and you can use a mind map to help sort out the outline.

For other related knowledge involved in the text, you should have a superficial understanding of it (an unfamiliar knowledge point can continuously lead to other knowledge, like a tree structure, layer by layer).

For the code examples in the article, be sure to type them yourself. This will help you understand and remember them better.

When you read it again, mark the points you think are important, and write down your related thoughts next to them (it can be the knowledge you have learned before that you think of, and you should integrate it).

Organize and combine your own thoughts and understanding, and re-output an article (you must have your own research and thinking).

Understand the basic technology

Focus on learning basic technologies: Basic technologies are the common foundation of various upper-level technologies. The purpose of thoroughly understanding basic technologies is to better understand the operating principles of the program and evolve more optimized products based on these basic technologies. This is a very good way to improve one's ability to draw inferences from one example.

Micro Habits

I recently read a book called "Micro Habits". It mentioned why people cannot stick to a habit for a long time:

They are ambitious, but they overestimate their abilities, and in their quest for change, they force themselves to do things beyond their capabilities. This is a mismatch between desire and ability.

The book proposes a very effective method:

Use a small amount of willpower to force yourself to do something. It doesn't take a lot of willpower to do one push-up or come up with a few ideas.

The benefits of mini habits include:

First, after completing your micro-goal, you are likely to continue to complete the "extra steps". This is because we want to do these positive behaviors, so once we start, our inner resistance will be reduced. The second benefit is inertia. Even if you don't exceed your micro-goal, your behavior will slowly develop into a micro-habit.

This month, I have incorporated micro habits into my daily life and have achieved some results. My micro goals include memorizing 10 words a day, doing 5 push-ups, reading for 5 minutes, and writing 50 words a day.

Tail

Come on 2018!