System Design & Management
Many tutorials and conference presentations... so much learning. The great thing about that is some of my approaches were confirmed as good practice, while I've also learned completely new methods for certain things, as well as ways to improve on key areas. For example, "vertical slice" architecture is a term I heard only recently, and the lectures I've watched have shown me that my approach is already solid but could be improved by better structuring the classes and objects within the class libraries, webAPI and UI projects so that they align with the feature-sets and avoid excessive coupling.
Achieving this low coupling and high cohesion will not just be beneficial for things like adaptability and changes in the future, but they will also help me incorporate specific system management functions more effectively. The ability to pause, deactivate/reactivate, and completely isolate particular features (at the function/method, class, feature and feature-set levels), is a good example of where these new lessons will help to better manage the system in general and especially as part of incident management.
I've also been learning new ways to improve my code. This part of the learning is definitely not a surprise for me, as my programming experience is completely self-guided. So there's a huge scope for me to keep improving until I can bring appropriately skilled and talented team members on board. At least now, some of the most obvious coding "faux pas" can be addressed before those future professionals chop my head off.
Although they'll probably still do that just because 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.