Recent grad exploring the realms of software engineering, with a passion for crafting seamless user experiences. 🚀 Currently delving into the world of open source and diving headfirst into Flutter development from scratch. Let's connect, learn, and build together! 💻✨ #SoftwareEngineering #UIUX #OpenSource #Flutter
Mobile development role- Flutter
Thank you for the kind words! I'm glad you found the article helpful. About the question: When you push changes to GitHub, you're uploading your changes from your local branch to a branch on the remote repository. The command git push origin main pushes your changes to the main branch on the remote repository. However, if you're working on a new feature or fixing a bug, it's a good practice to create a separate branch for your changes. For example, I created a branch called fix/division-by-zero-handling . To push changes to this branch, I used git push origin fix/division-by-zero-handling This command pushes changes to a branch named fix/division-by-zero-handling on the remote repository, keeping your work organized and making it easier to manage different features or bug fixes. Once your work is reviewed and approved, it can be merged into the main branch. Hope you have now understood it
About the late modifier, I have understood the 1st user case, which is; "it is used to declare non-nullable variable that will be initialized later in the code" but I have failed to understand the 2nd user case which is "lazy initialization", I don't know if I will understand more about it when I reach class