title: Fixed one thing, broke something else. What is the name of the pattern?
body: <p>How do you call the pattern or architecture of the system, that when you fix something in one place, you later notice that something is broken somewhere else? </p>
  
  <p>I am failing to come up with a concise name for that. It is the situation with the system when you lose confidence in that you or someone else is doing things right. You feel like you've lost control over complexity. In worst case it is the architecture where you afraid to do any change without thorough test coverage or rigorous testing. The pattern where you start to hate your job, because every minor code change is connected with enormous amount of time and effort, where you begin learning language with static typing or just start to do more "dumb coding" that "smart thinking" in hope that <code>coverage will warn you about mistakes</code>.</p>
  
  <p>Before this problem in software development can be dealt with, it needs to be defined in short and concise manner. Maybe you know an entry on jargon file or already coined this definition in your team?</p>
  
  <p>This word is needed to describe a bad architectural move. Quite often it is called <code>spaghetti code</code> or <code>smelly code</code>, but it not an exact description of the system that supports only this <code>hole patching</code> development process. The main characteristic here is that <code>every fix is likely the cause of new issue</code>. Sometimes the process is endless, because new people can not see the real cause, and repeat the mistakes over and over again reinventing the wheels on the way, etc.</p>