preface
I’ve been taking notes on Android lately, and I feel more and more detached from Android development. Android programmers aren’t as employed as they used to be, including myself, who started my new company as a mobile engineer, but didn’t differentiate between mobile and non-mobile.
Ten years ago, you didn’t know me, I didn’t know you.
When Android released SDK1.0 in 2008, I reminded a colleague to learn, and a year later he recommended me back to Android development. Android development has changed a lot for me, and I’ve finally caught a wave of things that I’ve always been slow to do.
I’ve always been a person who keeps work and life separate, so Android app development was a good fit for me, who was a mobile developer at the time. You’re making decisions that are best for you right now, aren’t you?
Because Android applications are relatively single in terms of business and framework, many applications can be handled by one person, which is more conducive to small workshops or small teams, and the communication nodes will be much less. With fewer points of communication, you’re likely to have more time and energy to focus on your own issues.
This is why I initially switched from J2EE to J2ME.
However, Lao Tzu was right: “Misfortune lies where happiness lies, and happiness lies where misfortune lies.”
Android app development alone may feel easy to control, but it’s easy to hit the professional ceiling. Android apps are so focused on one aspect that, to use the war metaphor, they can be just the trenches on the front line. You may be good at close quarters in the trenches, but it’s easier to see multiple angles from thousands of miles away, and focusing too much on “close quarters” can lead to missing the opportunity to develop a bigger picture.
Including the big picture of Android itself, which I suspect people like me who were early Android developers may not be able to explain.
To put it simply, as an Android app developer, you’re destined to be small in most cases.
pattern
And your pattern defines your career. Android app developers aren’t alone, and many front-end developers today face the same problem. Although H5 front-end is more efficient and flexible than Android, it can be dynamically deployed, but it still inevitably falls into a small pattern.
In 2011, when we were building an APP, we had to find someone on the back end to work with. I’ve tried to do the back-end myself, but I’m not up to it, because I’m a person who spends a lot of time with books (non-technology) and my family. But maybe IT was my own lack of focus and effort, and I was forced to focus on a single area of Android development.
The solution to the problem lies somewhere else. Otherwise, you would have taken care of it.
It was not until recently that I followed up some different technical fields and learned and imitated from people in different technical fields or non-technical fields that I gradually became less confused about the progress of technology. The skills I spent outside of the code helped me see the technology for what it was.
One day, your pattern is opened, the original problem is not a problem, even if it is still a problem, but no longer important.
The road to salvation
“Redemption” is for those, like me, who want to move forward in technology, but feel like they’ve wasted a lot of their time. There is always a hidden worry inside us, something we cannot solve, hoping that one day we will be “saved”, fulfilled and content.
So start with a theme to document your own path to salvation.
Always record something useful so people can find their way around. I have encountered many problems recently, and I need to summarize and sort them out slowly. Embracing problems is a good opportunity for my attitude and growth.
Save it for the next article, which will introduce an Android example. You can follow me if you like my article, and I will continue to share more Android technology dry goods in the future. Thank you for your support!