How do software design practices and development terms describe code quality and collaboration?

"anti-pattern a common software pattern that is used as a solution to recurring problems that is usually ineffective in solving the problem or introduces risks and other problems; a technical term for common “bad-habits” that can be found in software. 152 bike shedding a phenomenon in projects where a disproportionate amount of time is spent on trivial matters at the expense of spending adequate resources on more important matters. The term was applied to software development by Kamp [ 24 ] but derives from Parkinson’s law of triviality [31]. code smell a symptom or common pattern in source code that is usually indicative of a deeper problem or design flaw; smells are usually not bugs and may not cause problems in and of themselves, but instead indicate a pattern of carelessness or low quality of software design or implementation. 152 compile the process of translating code in a high-level programming language to a low level language such as assembly or machine code. continuous integration a software development/engineering process by which developer code is merged and shared on a frequent basis. Conway’s Law an observation that organizations that build software will inevitably design it as modeling the structure of the organization itself. Attributed to Melvin Conway (1967) who originally stated it as “organizations which design systems . . . are constrained to produce designs which are copies of the communication structures of these organizations”. copy pasta bad coding practice of copy-pasting code and making slight changes when a function or other control structure should be written instead. Copy-pasta practices often lead to poorly designed code, bugs or spaghetti code.. cruft anything that is left over, redundant or getting in the way; in the context of code cruft is code that is no longer needed, legacy or simply poorly written source code. 589 dead code a code segment that has no effect on a program either because it is unused or unreachable (the conditions involving the code will never be satisfied). 72 flowchart a diagram that represents an algorithm or process, showing steps as boxes connected by arrows which establish an order or flow. 17 idiom in the context of programming, an idiom is a commonly used pattern, expression or way of structuring code that is well-understood for users of the language. For example, a for-loop structure that iterates over elements in an array. May also refer to a programming design pattern.. 315, interactive a progr"