I firmly believe there is no such thing as a "bad" or a "good" architecture. It either fits the business needs from a technical perspective, or it doesn't. A technical design is always the result of a series of "choices" and "decisions" throughout the lifetime
(Don't?) Keep It Simple Stupid!
For as long as I can remember, the KISS (Keep It Simple Stupid) principle has been around to remind developers and businesses to approach a given problem with the easiest (or most simple) solution as possible.
Which basically means that the complexity of a software
Famous laws of Software development
Like any other field, the world of Software Development has some interesting and famous rules, principles and laws. Programmers, developers, managers and architects often use these in conversations, meetings and chats. More than often we tend to nod along, not willing to let our conversation
An introduction to Deployment Pipelines
With this post I would like to provide an introduction to concepts as Continuous Delivery and Deployment Pipelines, working as an extension for the known Continuous Integration process. This introduction is mostly abstract and "theoretical". The aim is to explain the concepts themselves
Using Fitness Functions to create Evolving Architectures
Don't worry, this is not a post on getting in shape, getting track of your overall fitness, or anything like that.
So nothing like this, no worries ;) :
Fitness functions
In this post, Fitness Functions are actually objective functions, used to summarize how close a prospective