Big ball of mud: a system with no recognizable structure.
大泥球(Big ball of mud)：系统的结构不清晰。
Wikipedia's entry on Big Ball of Mud also describes it very well, with a notable exhortation
Wikipedia关于大泥球的条目，还对其做了很好的描述，并提出了有建设性的意见
Keep adding code recklessly and, before you know it, you'll have created the dreaded Big Ball of Mud.
轻率地增加编码，不用多久，你就会造出一个可怕的大稀泥巴。
A Big Ball of Mud is a haphazardly structured, sprawling, sloppy, duct-tape-and-baling-wire, spaghetti-code jungle.
所谓的大泥球就是一个偶然结构的，伸展的，邋遢的，spaghetti代码的混合。
Wikipedia describes "Big Ball of Mud" as an anti-pattern 18: "a system without a recognizable structure." Here is Foote and Yoder's definition.
Wikipedia将“大泥球”描述成一种反模式18：“一个没有可识别结构的系统”。
There is no question that formal code reviews catch bugs and can delay the inevitable "big ball of mud" that all successful projects seem to turn into.
无疑规范的代码复审可以捕获错误，并推迟似乎所有成功项目最终都逃脱不了的“大泥球(big ball of mud)”宿命。
Yet, we all know that build scripts are central to creating the code the customer eventually uses and if those scripts are a big ball of mud, creating that software efficiently becomes challenging.
然而我们都知道，要创建客户最终使用的代码，构建脚本是中心，如果那些脚本败絮其中，那么要想有效地创建软件，就需要克服重重挑战。
Yet, we all know that build scripts are central to creating the code the customer eventually uses and if those scripts are a big ball of mud, creating that software efficiently becomes challenging.
然而我们都知道，要创建客户最终使用的代码，构建脚本是中心，如果那些脚本败絮其中，那么要想有效地创建软件，就需要克服重重挑战。
应用推荐