foreword
Tell a real story,
I met a front-end programmer last year. He is 37 years old. He can’t keep up with his thinking. He can’t write ten lines of code a day, and nine of them have bugs. .
His wife is in the same company as him. They are art designers and app page designers, but the pages made by his wife always have a sense of prosperity and prosperity, just like the mobile phone emoticons of their parents. Party A and Bosses are ugly.
So the couple were both laid off.
After being laid off, they went back to their hometown in Hubei and opened a steamed bun shop. Because the steamed stuffed buns they made were really not good, customers said that the steamed stuffed buns had bugs, and some of them forgot to put the stuffing .
So the bun shop closed down
Then I set up a local stall to sell simple fried skewers. I felt that the fried skewers sold by others were not fresh. As long as I grasped this aspect well, the business would definitely be good. When it sells, the reason is probably that the hand-cooked frying does not produce the taste.
With the rapid development of the technology industry, age has become a sensitive topic in the workplace for older programmers. Some people think that old age has led to their resignation, while ignoring their own reasons. Why do you think he was laid off? Why doesn’t he like buns and fried skewers? Is it his age?
As a manager you need technology more
In the technology industry, a large part of the career development of older programmers may transfer to management. However, many people think that once they become management, programmers can safely put down technology and focus on management. This view is incorrect.
Generally, current programmers work from the bottom to managers. If you lead a small team when you are in your 30s, although you don’t need to intervene in the underlying work, you only need to order it. You must be familiar with the overall framework. You need to know that if you want the train to run fast, you need a good locomotive.
At that time, my friend’s company had hired a technical director. He had been in the company for more than a month, and he hadn’t even figured out the project process of the company he was in charge of.
He was fired after only two months.
Again,
take Blaise Agüera y Arcas, a senior software engineer at Google (Google). Blaise Agüera y Arcas has maintained a technical focus and is actively involved in the technical team after taking on a management position. Under his leadership, Google's algorithm team has made several important breakthroughs. The example of Blaise Agüera y Arcas shows that management programmers can manage their work while keeping an eye on technical developments and leveraging their expertise in the technical field.
A manager who doesn't care about technology can't go far. Here is a more well-known example. The three founders of Mihayou are all technical backgrounds. They also did not let go of technology when they became bosses. So it is clear about the company's entire business process, which is one of the reasons for their success, not just because of love but also because of ability.
Now some older programmers always feel that
The decline in their own learning ability and adaptability, the pressure on physical and mental health is great, and they cannot compete with young people. I just blindly make excuses for myself, and I can't see my own advantages, such as contacts, technology, overall situation and so on.
It may be that many older programmers don't have it now, so they are panicking all day long.
at last
The dilemma of older programmers in the workplace is not insurmountable. As long as you maintain a learning attitude, improve your professional skills and soft skills, pay attention to your physical and mental health, expand your interpersonal relationships, build your personal brand, and make a good career plan, you will be able to find your place in the fierce competition.
Here is a joint learning material of Android framework family bucket compiled by Ali P7 architect and Google technical team.
I hope it will help you in your growth path. Due to the large content of the article and the limited space, the information has been organized into PDF documents. If you need the complete document of "Android Framework Advanced Study Guide", you can scan the card below to get it for free~
### **Chapter 1 System Startup Process Analysis**
● The first section Android startup overview
● Section 2 init.rc analysis
● Section 3 Zygote
● Interview questions
Chapter 2 Binder Analysis
● The first section macro understanding of Binder
● In the second section, the jni method registration of binder
● The third section binder driver
● Section 4 Data Structure
● The fifth section starts service_manager
● Section 6 Get service_manager
● Section 7 addService process
● Full analysis of Binder interview questions in the eighth section
Chapter 3 Handler Analysis
● Section 1 source code analysis
● Difficult questions in the second quarter
● Section 3 Handler common interview questions
Chapter 4 AMS Analysis
● Section 1 Introduction
● Section 2 Android Architecture
● Section 3 Communication Methods
● Section 4 System Startup Series
● Section 5 AMS
● Section 6 Analysis of AMS Interview Questions
Chapter 5 WMS Analysis
● Section 1 Activity and Window related concepts
● Section 2 Android window management service WindowManagerService calculates the size of the Activity window
● Section 3 Android window management service WindowManagerService analyzes the way windows are organized
● Section 4 Android window management service WindowManagerService for input method window (Input
● Section 5 Android window management service WindowManagerService for wallpaper window (Wallpap
● Section 6 Analysis of the process of calculating the Z-axis position of the window by the Android window management service WindowManagerService
● Section 7 Android Window Management Service WindowManagerService Displays the activation of the Activity component
● Section 8 Android Window Management Service WindowManagerService Switching Activity Window (A
● Section 9 Android window management service WindowManagerService principle analysis of display window animation
Chapter 6 Surface source code analysis
The first section creates the process and draws software and hardware
● Section 2 Double Buffering and SurfaceView Analysis
● Section 3 Overview of Android Graphics System
Chapter 7 Analysis of SurfaceFlinger Source Code Based on Android 12.0
● The first section builds the communication bridge between the application and SurfaceFlinger
● Section 2 SurfaceFlinger startup and message queue processing mechanism
● VSync of SurfaceFlinger in the third section (Part 1)
● VSync of SurfaceFlinger in the fourth quarter (middle)
● VSync of SurfaceFlinger in the fifth section (below)
Chapter 8 PKMS source code analysis
● Section 1 PKMS calling method
The second section PKMS startup process analysis
● Section 3 APK scanning
● Installation of APK in the fourth section
● Section 5 PKMS Permission Scanning
● Section 6 Silent Installation
● Section 7 requestPermissions source code process analysis
● Section 8 PKMS Interview Questions
Chapter 9 InputManagerService Source Code Analysis
● The first section Android Input input event processing flow (1)
● Section 2 Android Input input event processing flow (2)
● Section 3 Android Input input event processing flow (3)
Chapter 10 DisplayManagerService Source Code Analysis
● The first section DisplayManagerService starts
● Creation of DisplayAdapter and DisplayDevice in the second section
The third section DMS part of the process of turning on and off the screen
● Section 4 Brightness Adjustment
● Section 5 Proximity Sensor off-screen principle
● Section 6 Logical Display and Physical Display configuration update