I wanted to write this article about an obvious antipattern that I keep encountering over and over again in my career. It is sort of related to the Anemic Design Anti-Pattern1 but on a scale beyond the development part of a project.
It also turns into a cocky semi-rant at the end (you have been warned).
I have worked with many junior team members over the past years and tried to help them get better on their job and also make sure the project we work on stays clean and neat. Sometimes I needed to explain architecture layers, sometimes dependency injection, other times code and framework specifics and so on.
I am one of the lucky people to actually be able to work for a company that tries to create its own software solution and become a software publisher. We are a sufficiently big company with enough resources to achieve this, but without being too burdened by the heavy corporate organization that some other companies have. The original founder is still the CEO and his little brother is the CTO. Family business is the best business after all.