Geoson Solutions ^™

Over the past little while, my learning focus has continued to evolve from initial onboarding into more advanced, practical development and Azure-related concepts. Building on earlier foundations, I’ve been expanding my understanding of Azure Pipelines and Azure Application Insights, while using these ideas in real application work.

The focus of my work during this phase has been the development of the EzExpense Mobile and PC versions. Working across both platforms has required careful attention to UI behavior, responsiveness, data flow, and usability. This experience pushed me to think beyond simply implementing features and toward designing solutions that remain stable, maintainable, and user-friendly.

Alongside this development work, I’ve been exploring Azure Pipelines and how CI/CD workflows structure the way modern software is built, validated, and delivered. Learning how builds, tests, and deployments can be automated highlighted how critical consistency and repeatability are in reducing errors and ensuring reliable releases.

In parallel, I’ve also been learning about Azure Application Insights and the role of telemetry in production systems. Understanding performance monitoring, failure detection, and runtime analytics reinforced the importance of visibility once applications are deployed. Rather than reacting to issues after they surface, Application Insights enables proactive identification of exceptions, slow dependencies, and behavioral anomalies.

These Azure concepts have directly influenced how I approach application development. While designing screens, refining Power Fx logic, and structuring Dataverse tables, I’ve become more aware of how small implementation decisions can affect build reliability, runtime performance, and overall system stability.

Another important takeaway during this phase has been recognizing how automation and QA complement each other. Azure Pipelines strengthens validation through automated checks, while Application Insights provides insight into real-world application behavior. At the same time, QA remains essential for evaluating user experience, edge cases, and interaction flows that automation alone cannot fully capture.

Beyond technical growth, working in this environment has reinforced a broader engineering mindset. Development is not limited to building features. it includes designing reliable workflows, validating changes, monitoring performance, and continuously improving system behavior.

As I continue progressing, my goal is to further deepen my understanding of CI/CD practices, monitoring strategies, and scalable application design. Strengthening these areas will help me build solutions that are not only functional, but robust and production ready.