A modern programming language that makes developers happier.

kotlinlang

`Day15`
• Finished lesson 1 in Udacity's _<https://classroom.udacity.com/courses/ud9012|Developing Android Apps with Kotlin>_
• Completed Unit 1: developer.android's _<https://developer.android.com/courses/basic-android-kotlin-training/overview|Android Basics in Kotlin>_
• Worked on ReportBuilder Project
• Reviewed <https://developer.android.com/jetpack/guide#separation-of-concerns|Separation of Concern>
• Started reviewing <https://developer.android.com/training/dependency-injection/manual|Dependency Injection>
`Self-Comment`
• The days are blending in together. I'll have to do a better job reporting before sleeping! Busy and productive day overall. Both the Udacity course and codelabs on developer.android are basically the same so far. I had finished about 60% of Udacity's unit 1  yesterday, completed the Codelabs for Unit 1, then went back and finished Udacity's about an hour ago. I'm watching the videos somewhere between x1.5 and x2 so it's comical when it swaps back to x1 and they talk like I put the video in slow motion.. Anyways, I prefer the codelabs and after completing both, I feel it's not efficient as the material is near identical. Will be sticking with the codelabs as I felt it had more content and better approach than the Udacity course. I'm not sure if I should be skipping to more codelabs as I want to fill in the gaps before taking on too much. Almost bought a course that goes over Android including frameworks, libraries, and such. However, decided against it for now as the information is going to be identical to what I can learn in codelabs for free. 
• Lightbulb went off at somepoint today and acted on it. So went in the RPB and started hacking away at code from the start. Not sure why it took me so long to go back and use near brute force for this project. Create a few data classes and logic classes, then just throw everything in the main file (I'm sure my code is cleaner than I make it sound.. lol). Anyways, good progress on it!
• SoC is easy to make sense of but difficult to apply. I think this will just come with practice
• I believe one reason I'm stumped in my Notes Project is due to following Hilt from how others have implemented it without actually understanding what it's doing. Would like to practice using manual DI to get a better understanding
`Goals Tomorrow`
1. Complete <https://developer.android.com/courses/pathways/android-basics-kotlin-unit-2-pathway-1#codelab-https://developer.android.com/codelabs/basic-android-kotlin-training-classes-and-inheritance|Android Basics Kotlin Unit 2>
2. Work on RPB
3. Review and practice with Dependency Injection
4. Keep breaking down <https://developer.android.com/jetpack/guide|App Architecture> over the week
5. Work on Notes Project if feeling inspired. :)

image.png

Working on two projects - note and reportbuilder? Rooting for you. :muscle: What is SoC in your context? Only SoC I know is system on chip lol

I heard a good explanation the other day defining Separation of Concerns.

"Every functions, class, or interface should be made as small as reasonably possible. " (a.k.a. Modularity)

Ohhh modularity :slightly_smiling_face: Totally agree _“easy to make sense of but difficult to apply”_