A DotNet developer’s note on Technology Radar V28

As a new Technology Radar release with a bunch of interesting techs, a few drew my attention. Techniques Applying product management to internal platforms: product mindset includes a roadmap, value to biz, and consumer experience enhancement. CI/CD infrastructure as a service: Our team has been using Jenkins hosted on-prem and started moving to Azure DevOps.… Continue reading A DotNet developer’s note on Technology Radar V28

A DotNet developer’s view about Technology Radar V26

As a new Technology Radar release with a bunch of interesting techs, a few drew my attention. Techniques Single team remote wall. This can be useful in a remote team. Documentation quadrantsDocumentation can be one of these. Tutorials, Discussions, How-To Guides, or References. And more tips on documentation. Rethinking remote standups. The daily stand-up is… Continue reading A DotNet developer’s view about Technology Radar V26

Domain centric architiecture – best refactoring example

One great example of refactoring data-centric .net application into domain-centric architecture is this. https://app.pluralsight.com/library/courses/n-tier-apps-part1/table-of-contents This training was released in 2012, which is 9 years old. But, this is the best example for me to apply in our company and myself, because 1) this course targets a legacy code, which we have in areas and wasn’t… Continue reading Domain centric architiecture – best refactoring example

4 Types of Event-Driven Architecture by Martin Fowler

Event Notification Address change in CRM can be sent to  Quoting System through the event. e.g. address changed. – Reverse the dependency from CRM to Quote system. – Message becomes a thing(object) to record and pass around. – events vs commands – pub/sub is nice as subscribers can sub independently.Cons: How to know what’s happening… Continue reading 4 Types of Event-Driven Architecture by Martin Fowler

Clean Architecture

Given that the number one reason why Unit Test fails is the code is not testable which make the unit test difficult, costly, un-maintainable, making the application layer independent through the interface is the most important concept in the clean architecture.