In previous article I discussed how to decompose an application into an architectural design using volatility based decomposition. I now want to show how the architecture can help you with your project planning.
if you spent time looking at the systems in the wild you will note that the systems are way to complex and have many many relationships between internal components. Its the relationships between the code structures that make a systems difficult to work on. You might need to work on something as simple like this.… Read More »
In previous articles I discussed the different ways a use case can be broken down into services. In the following article I will extend on that and show how the back-end should drive your front-end.
I received a fresh laptop this week and after installing a fresh copy of Visual Studio 2017 Professional, I started getting the following error when trying to add a reference to a project.
Volatility based decomposition is way to break a system up into components that can absorb change and result in a stable system. It builds on SOLID principles and can be viewed as the opposite of functional decomposition.
Functional decomposition is a way to decompose \ break down a system into its most simplistic components and functions for rapid application development.
I noticed something interesting today with .net core. The Object.GetHashCode() method is not returning consistent values.The values are only consistent for the instance of the .net core process.
Recently I had to do a implementation of SAML2 within .Net, .Net does not have any native support for SAML2 and as a result I had to approach a 3rd party provider called Component Space. Their support is really first class.
Say what? Impossible…
A few months ago I took on a little side project to try and write my own version of a classic game from the 80’s – Xonix. I have worked on and off on it since then, more off than on and spent a total of 7 days on it. This little game has given… Read More »