Android Developer

My journey as a software developer began at university. I had a passion for video games and that was my motivator. "I want to learn how to make games" I said. A few years later I have this amazing skill to develop software applications and of course I also know how to make games.  
 
During my senior years at school, I also became a tutor as well as a student assistant. In that role I was responsible with tutoring software engineering students with their practical work. This included algorithm development, data structures, network programming (TCP/UDP) and object-oriented programming principles. This experience helped to solidify my own understanding of these concepts. I value this experience so much because I learnt from there how to look at someone else's work/code and help them solve their problem. This is a skill critical in working effectively in a development team and with a client. I learnt how to listen to someone attentively in order to understand their problem and then provide working solutions for them. 
 
After school I began working for Discovery Ltd as a software developer. During this time, I acquired a lot of skills within the development lifecycle. I have worked on developing microservices using spring boot and maven. These services are consumed by the mobile clients. I also work on the Android application which has more than a million downloads on the play store. I gained immense experience in designing, creating and releasing an application that goes on to the store with success. I have experience with developing mobile apps with maintainable and robust architectures such as MVP and MVi. I have been exposed to integrating third party libraries (Facebook, Uber and Cambridge Mobile Telematics) into an app. After 3 years I have grown into an Android developer with skills to consume restful API's or to create API's using Swagger and Raml.  
 
In a nutshell, I see myself as a problem solver and the software is just a tool. If the problem needs new tools, I can adapt and bring the new tools in. For example, I worked on a project which had no architecture and I had to learn a new architecture and implement it in the project. I began as a .NET developer making web apps and I have grown into a Java and Kotlin mobile programmer. Therefore, It's not about the tools, it's about the solution.