Where is it going?
Recently I remembered my experience of working in a payment system, which currently doesn’t appear to be functioning. I had been working there for many years, definitely longer than I needed, so there are many things to remember. Today I want to tell a story about how the company turned my colleague and me into an Android developer and why it wasn’t so beneficial for me.
The story had its place a long time ago, in 2018, you might remember those years: Android was as popular as it is nowadays and lots of companies were developing applications for that, and the company where I was working wasn’t left behind. At the same time a project, written in C++, in which my colleague and I were involved, came to its decline phase: support and support, very few features, and no plan for further development. It isn’t a figure of speech because there is a concept of the product life cycle and software is also a product, but let’s leave this discussion for another time. The company stuck to a very calm position relating to declining projects: if employees want to work then let, them work as they can, we’re not going to fire them (as well as not going to raise their salaries). Consequently, when during a conversation with our manager my colleague and I were offered to switch to an Android development without prior experience in this field we took this offer immediately.
Particular conditions also sounded very interesting: develop an Android app from scratch, which contains several tens of screens and interacts with a backend and so on, and by the way, you’ll work with an analyst/project manager and an experienced coach from a flagship company’s project. Amazing! I’ll skip functional description because it doesn’t play a major role.
Having looked at Java documentation and an Android project, I realized that Java is quite close to C++ from which someone removed all the most complicated parts, and the main difficulty is Android SDK itself: the activity lifecycle, fragment lifecycle, branched screen transitions… The coach helped with it: “You need to use Moxy, Cicerone, RxJava, Retrofit, and of course Dagger”. No sooner said than done, though not all of those technologies look pretty obvious for a C++ developer, but they make life simpler.
The story has turned out to be long, so let’s go on with it another time.
#job #IT #Android #Java #memories #ToBeContinued #interesting_tasks
Recently I remembered my experience of working in a payment system, which currently doesn’t appear to be functioning. I had been working there for many years, definitely longer than I needed, so there are many things to remember. Today I want to tell a story about how the company turned my colleague and me into an Android developer and why it wasn’t so beneficial for me.
The story had its place a long time ago, in 2018, you might remember those years: Android was as popular as it is nowadays and lots of companies were developing applications for that, and the company where I was working wasn’t left behind. At the same time a project, written in C++, in which my colleague and I were involved, came to its decline phase: support and support, very few features, and no plan for further development. It isn’t a figure of speech because there is a concept of the product life cycle and software is also a product, but let’s leave this discussion for another time. The company stuck to a very calm position relating to declining projects: if employees want to work then let, them work as they can, we’re not going to fire them (as well as not going to raise their salaries). Consequently, when during a conversation with our manager my colleague and I were offered to switch to an Android development without prior experience in this field we took this offer immediately.
Particular conditions also sounded very interesting: develop an Android app from scratch, which contains several tens of screens and interacts with a backend and so on, and by the way, you’ll work with an analyst/project manager and an experienced coach from a flagship company’s project. Amazing! I’ll skip functional description because it doesn’t play a major role.
Having looked at Java documentation and an Android project, I realized that Java is quite close to C++ from which someone removed all the most complicated parts, and the main difficulty is Android SDK itself: the activity lifecycle, fragment lifecycle, branched screen transitions… The coach helped with it: “You need to use Moxy, Cicerone, RxJava, Retrofit, and of course Dagger”. No sooner said than done, though not all of those technologies look pretty obvious for a C++ developer, but they make life simpler.
The story has turned out to be long, so let’s go on with it another time.
#job #IT #Android #Java #memories #ToBeContinued #interesting_tasks
👏2