PS: If you like something, just go ahead and do it. No matter what the outcome is, it will be a very good experience.
During this period of time, I resigned for some reason and took a break for about two weeks. During this time, I explored the alleys around that I had never been to before and saw many interesting things on the streets. It turns out that there are still many people doing what they love on weekdays. Actually, clocking in to work is just one of many lifestyles and not a necessary choice. I hope that one day I can have some choices or make changes.
Although the days without work are leisurely, reality tells me that I have to continue to invest in my work. During this time, I have actually made some improvements to my resume, but I haven't sent it out yet. By the way, let's talk about resumes. The layout of a resume is really important. You should avoid obvious formatting errors, such as the capitalization of English words in the skills description. You should understand which technical points match your work experience. Of course, you must pay special attention to the content written on the resume. The conciseness and completeness of the resume are key factors for HR to decide whether to invite you for an interview. I suggest that students who are still looking for a job and have not received interview invitations should modify their resumes. This situation is often due to problems with the resume.
From the requirements for Android recruitment, you will find a phenomenon, such as the use of Kotlin to develop complete projects that have been launched, and preference for Flutter. From this point of view, my own technological updates have been a bit slow. Although I bought relevant books in the first half of the year, I haven't really read them. I have realized this for a long time, but I have always lacked action. This part can only be postponed to the second half of the year. There are still quite a few Android positions available, so those who are worried about this aspect can rest assured. Just focus on improving your technical skills.
In recent interviews, I have encountered both mediocre interviewers and excellent ones. During the interview process, I also realized my own shortcomings. I have a good breadth of knowledge in terms of learning related knowledge, but I lack depth. Especially when a question becomes more and more difficult, I don't know how to answer it. I can only try my best to answer with what I believe is the correct answer. This kind of interview really pushes and improves myself. This kind of communication was not present in my previous work, mainly because the level of my previous team was really disappointing.
Let's talk about my public account. I haven't updated it during this period, and many people have unfollowed. I think this is reasonable. A technical account should be continuously updated, but it is impossible to create original content every day because it takes time to write a good article. Some things I come across are not suitable for writing an article, so I usually organize them into corresponding notes for future reference. In the future, I will continue to maintain a certain update frequency and hope that the articles I write will have more depth. In addition, my current work may involve EPG development, so I will also summarize articles related to EPG development in the future. Thank you to all the followers who have been supporting and following me. Let's work hard and progress together.