Latest Posts - Page 119 of 198

June 12, 2019June 3, 2019 Common Anti-Patterns

The Warm Bodies AntiPattern – Not a Cool Situation

We all know that more is always better except when it is not. The challenge of quality and quantity is a common anti-pattern for software development. We take a look at it in this episode about the warm bodies approach. Defining the Warm Bodies Anti-Pattern There are several definitions of this anti-pattern. In this episode, we use the Daxx site definition to drive our discussion. [Click Here to See The Page] “This antipattern seems, at first, to have more to do with the structure of your company than the structure of your software. That being said, problems with the former can have unfortunate consequences for the latter. “Warm bodies” are people who work for your company, but aren’t deeply invested... Read more

June 10, 2019May 31, 2019 Common Anti-Patterns

Autogenerated Stovepipe – An Anti-Pattern

In an effort to re-use our previous work, we can over-simplify a solution. One such situation is when we grow from a stand-alone system to a distributed one. This particular anti-pattern is a facet of the autogenerated stovepipe. Even the best solution in one case is not always going to be a good one to move to an enterprise or a distributed approach. Defining the Autogenerated Stovepipe Anti-Pattern There are several definitions of this anti-pattern. In this episode, we use the source-making definition to drive our discussion. [Click Here to See The Page] “This AntiPattern occurs when migrating an existing software system to a distributed infrastructure. An Autogenerated Stovepipe arises when converting the existing software interfaces to distributed interfaces. If... Read more

June 7, 2019May 30, 2019 Common Anti-Patterns

Wolf Ticket AntiPattern – Not What It Seems

We often look at vendors and standards for a way to improve productivity. There is nothing wrong with this and it even is a best practice. However, not everyone follows a standard entirely or even in the same way. This situation can lead you to a wolf ticket antipattern. In short, the product you choose is not what it seems. Defining the Wolf Ticket AntiPattern I find the origin of this anti-pattern name to be instrumental in defining it. [Click Here to See The Page] “The term wolf ticket originates from popular slang. In slang, a wolf ticket is an unofficially issued event pass (e.g. for a rock concert) that is sold by unscrupulous ticket scalpers.“ An essential piece of... Read more

June 5, 2019May 25, 2019 Common Anti-Patterns

Defining The Jumble AntiPattern

In this episode, we tackle a higher form of the Spaghetti Code Anti-Pattern. While that is a code-level issue, the jumble antipattern shows up in the architecture. There are almost always going to be horizontal and vertical aspects of a design. Some facets are specific to the solution while others are common across multiple applications. When we confuse and tightly couple these aspects then it turns into a jumble Defining the Jumble AntiPattern The C2 wiki makes another appearance as we look into a definition for this anti-pattern. [Click Here to See The Page] “”When horizontal and vertical design elements are intermixed, an unstable architecture results. Vertical design elements are dependent upon the individual application and specific software implementations. Horizontal... Read more

June 3, 2019May 25, 2019 Common Anti-Patterns

The Input Kludge AntiPattern

It is hard to think of the word “kludge” and anything other than an anti-pattern. Thus, the input kludge antipattern is an obvious name. This example of how not to code is focused on the concept of garbage in – garbage out. When you allow data with questionable quality to enter your system, then it should be no surprise that the solution suffers in quality. Defining the Input Kludge AntiPattern The best definition I found this time around is on the DZone site listed with several other anti-patterns. [Click Here to See The Page] “An input kludge is a type of failure in software (an anti-pattern) where simple user input is not handled properly. This may cause a buffer overflow security hole, issues during... Read more

May 31, 2019May 18, 2019 Common Anti-Patterns

The Ambiguous Viewpoint AntiPattern

The ambiguous viewpoint anti-pattern is one that goes to the heart of object-oriented design. We want to abstract and isolate functionality in a way that follows a pattern of logic. This goal is often achieved, in part, through segmenting functionality by viewpoint. Thus, we have the business, data, and view related code grouped in their separate areas. Defining the Ambiguous Viewpoint AntiPattern I found a good explanation of this anti-pattern on a page worth checking out for several others as well. [Click Here to See The Page] “Object-oriented analysis and design models are often presented without clarifying the viewpoint represented by the model. By default, this models denote an implementation viewpoint that is potentially the least useful. Mixed viewpoints don’t allow... Read more