When building my first app with the Room Database feature, it was a challenge and I could not get the database to work. In order to resolve the issue, I followed these 4 steps. Step 1, review the code. I started by reviewing my code to try to identify any glaring issues. Then, I looked closely at working examples to see if I could identify any patterns. In my project, I noticed my initial code compared to that of my tutor differed in how our projects were organized in packages and files. My project lacked any organization. This led to step 2, where I began to ask clarifying questions and in this case asked my tutor why he separated items into a database package and the UI in another package etc. He began to reiterate the importance of separation of concerns and clean architecture and reviewed MVVM with me. Next, in step 3, I sought out and leveraged any available resources including videos on YouTube (I am a visual learner), lessons from class, documentation, articles, and code labs to learn more. I was curious to learn more about how projects with databases were structured to work. I used a developer's best friend, the Google search engine, to investigate and gather information. Lastly, in step 4 I revised my code making the necessary changes based on the information I discovered in the previous steps. My 4 step cycle continued until I was able to successfully get the Room database to work in my android application. I use these 4 steps of problem-solving for any and all coding problems. When reflecting on things I would do differently if faced with the same problem I think I would implement these steps sooner. I admit I get frustrated and imposter syndrome kicks in when I face a coding challenge. Therefore, I have to remind myself to get past that feeling and follow my 4 easy steps to logically solve any coding problem. I hope these 4 steps help you the next time you encounter a challenge.

I am most proud of the first app project I created. The instructions were to make a simple Celsius and Fahrenheit temperature app converter. We were given basic instructions and even a video demo and photos of what the finished product could look like. Most people created an app identical to our instructor’s example; however, I chose to have fun with the project and add my creative spin to the app design. Since it was a temperature app, I wanted it to provide simple conversions, but I also wanted people to use it. Particularly, I thought, what would make me want to use this app? This is an important part of my development process. After some thought, my inspiration came to me and I added a hot picture of my favorite rapper, Nelly, to my app design/layout. And because he made a famous song about “et gettin hot in here,” I used that as the theme for my app project. When I presented my app to the class, my teacher shared that my app was her favorite. Of course, this is a fond memory for me and a highlight in my career journey to becoming a mobile engineer, which is why I love to share this app with others and tell my story. Not only did I fall in love with android development while creating this app I also had fun developing the app. If you are not having fun, you are doing it wrong, and this was a fun project that I smile about often when I think about it. Not only that, I set the bar high after this project, and my peers brought their ‘A’ game for all projects after this one, and I loved the fun, competitive nature of it all. Check out my very first app project at https://github.com/MissChurchill/Smart_Converter.