Tag: misconceptions
-
The CI/CD Misconception
The terms CI (continuous integration), CD (continuous delivery), and the umbrella term CI/CD are often misunderstood and misused. Many think that continuous integration is primarily about automation and tooling, i.e., having an automated build pipeline, often evidenced by them referring to their pipeline as “the CI”. They are unaware that…
-
Taste Your Own Soup
Imagine this scenario: A restaurant cook learned from their grandmother the secret of her tasty soup. “Always put a tablespoon of salt in your soup”. And so they follow the advice, every day, no exception – and the customer reviews are, well, not great. “Disgusting”, says a food critic in…
-
SRP Misunderstood
The Single Reponsibility Principle (SRP) is commonly misunderstood. Often you might hear explanations like “a class should do only one thing”, sometimes even extended to methods. Here’s a heuristic that I think might help: This may not only lead to less-bad code, but as a side effect also to a…
-
CI/CD is Not a Tool
CI/CD is something you do, not something you have. Having an automated build and deployment pipeline is part of it, but there’s nothing inherently “continuous” about Jenkins or GitHub Actions. I have no problem with tool-focused terms like “CI pipeline” if the intention is to imply that the tool is…
-
The SRP is not SoC
The Single Responsibility Principle (SRP) aims to increase cohesion and to minimize the risk of breaking functionality through seemingly unrelated code changes. However, many misunderstand the SRP, thinking it means a class should only do one thing, or that the SRP can be applied to functions or architectural layers rather…
Raimund Krämer 