This is a preamble to my series Enterprise FizzBuzz, Dependency Inversion, and Capitalism. Generally, the series is written for an audience that is likely familiar with the titular topical, but I will still use this preamble to quickly introduce them. I will end this preamble with the questions that I want to answer in the series.

FizzBuzz

FizzBuzz is a very simple programming exercise that is often used as a sort of litmus test for basic programming ability. The exercise can be solved in various ways, and any given solution may be dead-simple, overcomplicated, or intricate, and can thus be a showcase of one’s cleverness, technical skill, and imagination - some have called it the Programmer’s Stairway to Heaven.

Rosetta Code defines it as follows:

Write a program that prints the integers from 1 to 100 (inclusive).

But:
  for multiples of three, print "Fizz" instead of the number;
  for multiples of five, print "Buzz" instead of the number;
  for multiples of both three and five, print "FizzBuzz"  instead of the number.

A solution in Python:

def fizzbuzz() -> None:
    for i in range(1, 101):
        if i % 15 == 0:
            print("FizzBuzz")
        elif i % 3 == 0:
            print("Fizz")
        elif i % 5 == 0:
            print("Buzz")
        else:
            print(i)

fizzbuzz()

Enterprise FizzBuzz

Enterprise FizzBuzz is a joke term poking fun at seemingly overengineered or at least wildly intransparent architectures of large scale organizations, with it’s root perhaps in the actual implementation FizzBuzzEnterpriseEdition in Java. Just to give you an idea of what I mean, here is the Main.java file in which the FizzBuzz is actually executed:

package com.seriouscompany.business.java.fizzbuzz.packagenamingpackage.impl;

import org.springframework.context.ApplicationContext;
import org.springframework.context.ConfigurableApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;

import com.seriouscompany.business.java.fizzbuzz.packagenamingpackage.impl.parameters.DefaultFizzBuzzUpperLimitParameter;
import com.seriouscompany.business.java.fizzbuzz.packagenamingpackage.interfaces.FizzBuzz;
import com.seriouscompany.business.java.fizzbuzz.packagenamingpackage.interfaces.parameters.FizzBuzzUpperLimitParameter;

/**
 * Main
 */
public final class Main {

    /**
     * @param args
     */
    public static void main(final String[] args) {
        final ApplicationContext context = new ClassPathXmlApplicationContext(Constants.SPRING_XML);
        final FizzBuzz myFizzBuzz = (FizzBuzz) context.getBean(Constants.STANDARD_FIZZ_BUZZ);
        final FizzBuzzUpperLimitParameter fizzBuzzUpperLimit = new DefaultFizzBuzzUpperLimitParameter();
        myFizzBuzz.fizzBuzz(fizzBuzzUpperLimit.obtainUpperLimitValue());

        ((ConfigurableApplicationContext) context).close();

    }

}

Dependency Inversion

In object-oriented design, the dependency inversion principle is a specific methodology for loosely coupled software modules. When following this principle, the conventional dependency relationships established from high-level, policy-setting modules to low-level, dependency modules are reversed, thus rendering high-level modules independent of the low-level module implementation details.

TODO

Capitalism

TODO

◻