盖尔-沙普利算法
I realized something fascinating the other day: I realized that, as a startup entrepreneur and founder, I’m a builder of systems.
前几天，我意识到了一件令人着迷的事情：我意识到，作为一名初创企业家和创始人，我是系统构建者。
In other words, my entire job as a founder is to build and connect interdependent systems that (hopefully) work exceedingly well together.
换句话说，我作为创始人的整个工作是建立并连接相互依存的系统，这些系统(希望)能够很好地协同工作。
And, if I can construct those systems in a way that’s both simple and approachable enough to be understood and to excite others, then, it’ll be enough to convince independent, creative, and motivated people to join in my efforts to engineer even more systems (and even more relationships between those systems) that will eventually coalesce into the form of a world-class organization.
而且，如果我能够以一种既简单又易于使用的方式构建这些系统，使其易于理解并激发其他人的兴趣，那么就足以说服独立，有创造力和积极性的人们加入我的工作，以进行更多的工程设计系统( 甚至这些系统之间的更多关系 )，最终将合并为世界一流的组织形式。
I mean, what is a business if not a collection of systems, organized in a way to maximize throughput, optimize performance, and produce out-sized results (i.e. profits)?
我的意思是，如果不是系统集合，那么组织的业务是如何以最大化吞吐量，优化性能并产生超额结果(即利润)的方式进行的？
And this is where startups have an unbelievable advantage over older and much larger companies: A startup has the opportunity to decide, for itself, not only what the fundamental and principal systems will be and how they will operate, but also the way in which the organization decides on what new systems to build and how they will integrate and be added to the existing, larger metasystem.
在这里，初创公司比起规模更大的公司具有不可思议的优势：初创公司有机会自己决定基本系统和主要系统的类型以及它们的运作方式，以及决策方式。组织决定要构建什么新 系统 ，以及如何将其集成并添加到现有的大型元系统中。
And the “meta system” is simply the collection of beliefs and the resulting behaviors that are have been generalized and normalized across the entire organism. One might call this organizational culture; hopefully, it’s one built on trust.
而“元系统”只是信念的集合以及由此产生的行为，这些信念已在整个有机体中得到了概括和归一化。 人们可能将这种组织文化称为“组织文化”。 希望这是建立在信任之上的 。
Gall’s Law is especially applicable and important for new companies — they need to take the time the necessary time to intentionally and explicitly think upon the systems that they use so that they will have a fighting chance to construct their world-changing ideas into real services and products that people truly want.
盖尔定律对新公司尤其适用，对新公司也很重要-他们需要花一些时间，有意识地，明确地思考他们使用的系统，以便他们有很大的机会将改变世界的想法构建成真实的服务，人们真正想要的产品。
You see, John Gall’s work has become the rule of thumb for systems design and has been used as a very strong argument for underspecification (which is where all startups begin):
您会看到， 约翰·加尔(John Gall)的工作已成为系统设计的经验法则，并被用作规格不足(这是所有初创公司开始的地方)的非常有力的论据：
A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a simple working system.
总是可以找到一个有效的复杂系统，它是从一个有效的简单系统演变而来的。 从头开始设计的复杂系统永远无法工作，也无法进行修补以使其正常工作。 您必须从一个简单的工作系统开始。
This is where startups have to be hyper-vigilant and emotionally aware and mature enough to know that they can do irreparable and permanent harm to their chances of success if they, either intentionally or accidentally, divorce themselves from the foundational system(s) that made their unique insight actually usable.
在这里，初创公司必须保持高度警惕，并在情绪上足够敏感，并且要足够成熟，才能知道如果他们有意或无意地将自己脱离了成功的基础体系，会对成功机会造成不可挽回的永久损害。他们独特的见解实际上是有用的。
I know because I’ve done this to myself in the past: I’ve built over-complicated and over-engineered systems and introduced them to my teams only to discover that they’ve done much more harm than good!
我知道，因为过去我对自己这样做：我构建了过于复杂和过度工程化的系统，并将其介绍给我的团队，只是发现它们的弊大于利！
In addition, some businesses codify these principle and original systems into mission or vision statements or prop them up as part of their corporate value statements while others will not. Even the act of codifying an understood and used system is an intentional decision by the founding team and leadership!
此外，有些企业将这些原则和原始系统编纂为使命或愿景陈述，或将其作为公司价值陈述的一部分进行支撑，而其他企业则没有。 甚至将已理解和使用过的系统编成代码的行为也是创始团队和领导者的有意决定！
And the temptation to over-engineer something (anything!) is already quite large; add a bit of business momentum, a few new hires, a smidge (or a lot) of venture capital, and a product that seems to be working, and you’ll suddenly wake up one morning and realize that you and your team is completely bloated and overweight with dozens of barely-used SaaS web services and a ton of (made-up) processes that, with an honest look, appear to exist for their own sake.
并且过度设计某些东西(任何东西！)的诱惑已经相当大了。 加上一些业务动力，一些新员工，一小部分(或很多)风险投资以及一种似乎有效的产品，您会在一个早晨突然醒来，意识到您和您的团队已经完全数十种几乎未使用的SaaS Web服务和大量(虚构的)进程processes肿和超重，这些进程看上去很诚实，似乎是为自己而存在的。
Good job startup founder — you just played yourself.
做得好创业的创始人-您只是扮演自己。
And we had such a good thing going! You started simply and things were working just fine and seemingly overnight you’ve backed yourself into a complex web of systems that “cannot be patched up to make it work” — you’re going to have to nuke a few things to get back to the baseline and the foundational “gem” that was working.
而且我们做得很好！ 您刚开始时一切都很好，似乎一夜之间，您已经将自己备份到一个复杂的系统网络中，“无法对其进行补丁以使其正常工作” –您将不得不做一些事情以恢复到原来的状态。基线和起作用的基础“宝石”。
This is why most larger companies can’t compete against the much smaller and more agile startups — the cost of reverse engineering or deconstructing and dismantling a dysfunctional, complex system is oftentimes too large and too destructive to be worth the effort!
这就是为什么大多数大型公司无法与规模更小，更敏捷的初创公司竞争的原因–逆向工程或解构和拆除功能失调的复杂系统的成本通常太大，破坏性太大，不值得付出努力！
Consequently, the dysfunctional system is “good enough” for most people and the larger organization and very few folks are motivated to “raise the white flag” and advocate for what is truly required: Starting over with a working, simple system.
因此，功能失调的系统对大多数人和较大的组织来说“足够好”，很少有人愿意“举起白旗”并倡导真正需要的东西：从一个工作，简单的系统开始。
Obviously, startups that have intentionally built a culture of introspection and ruthlessly review their outdated and outmoded systems will fare much, much better than their peers and, of course, their larger enterprise competitors.
显然，有意建立自省文化并无情地审查其过时和过时的系统的初创公司的表现要好得多，远胜于同行，当然也比其较大的企业竞争对手。
Startups begin their lives with simple systems and naturally expand and grow new systems that are generally bolted-on in a fashion that most would consider random and hodge-podge. The collection of simple systems form complex systems and some of these work for a long time while others break down very quickly.
初创公司以简单的系统开始他们的生活，并自然地扩展和发展通常以大多数人认为是随机的和杂乱无章的方式固定的新系统。 简单系统的集合形成了复杂的系统，其中一些工作了很长时间，而另一些则很快崩溃了。
The organization that recognizes the delta of successful and unsuccessful integrations between the new systems and the old are going to succeed (and survive) much longer than those that willfully ignore the dysfunction or naively assume that it’ll all work itself out along the way.
该组织认识到新系统与旧系统之间成功和不成功的整合的增量比那些愿意忽略功能失调或天真的认为它会在整个过程中自行解决的人要成功(并生存)更长。
And the organizations that not only recognize quickly and intentionally work together actively towards fixing the issue but also are willing to, if the situation requires extreme action, dismantle entire systems in order to build new, simpler ones to support the weight of a new and altogether different organization (startups can fundamentally change as often as every 6 months!).
而且，不仅要Swift并有意识地积极合作以解决问题的组织，而且还愿意在情况需要采取极端行动的情况下拆除整个系统，以构建新的，更简单的系统来支撑新系统的重量。不同的组织(从根本上说，初创公司每6个月可以更改一次！)。
Needless to say, it is exceedingly difficult to strategically and tactically keep systems simple while adding to them wisely and intentionally as the organization scales.
不用说，要在战略上和战术上保持系统简单，同时随着组织规模的扩大而明智地和有意地添加它们，是极其困难的。
This isn’t to say that I’m an expert; rather, I’m emotionally aware enough to know (and have empirical evidence) that organizations tend toward chaos and entropy without a steady and consistent review of not just what is being done but how it’s being done.
这并不是说我是专家； 相反，我在情感上足够了解，可以知道(并有经验证据)，组织会趋向于混乱和熵，而不是对所做的事情及其进行的方式进行不间断的，一致的审查。
And, if I’m to be even more honest, I know that I tend to introduce entropy to systems if I’m not careful! In fact, I know that even if I try my hardest it’ll be an uphill battle every single step of the way.
而且，如果说实话，我知道如果不注意的话，我倾向于将熵引入系统！ 实际上，我知道，即使我尽力而为，每步都将是一场艰苦的战斗。
It is in the team’s best interest to do some, if not all, of the following:
进行某些(如果不是全部)以下活动符合团队的最大利益：
- Schedule in time to review your systems by team and/or organizational department (e.g. ops, engineering, marketing, sales, etc.).
及时安排团队和/或组织部门(例如，操作，工程，市场营销，销售等)对系统进行审查。
- Identify, as best as you can, the principle (original) simple system that eventually became a complex one and clarifies clearly the (expected) outputs and the persons that should be involved.
尽可能地确定最终成为复杂系统的原理(原始)简单系统，并明确阐明(预期的)输出结果和应涉及的人员。
- Outline and identify the interdependencies of the system that’s being reviewed; that is to say, the other systems that have direct interplay with the one in the review.
概述并确定正在审查的系统的相互依赖性； 也就是说，与评论中的系统有直接相互作用的其他系统。
- Ruthlessly judge the system and adjust, prune, or outright destroy it and then build a new, simpler version (or maybe go back to the Genesis version).
无情地判断系统，然后调整，修剪或彻底销毁它，然后构建一个新的，更简单的版本(或者回到Genesis版本)。
- Consensus might be required or not, but, regardless of how your team makes decisions, make sure that everyone is on board with the new (and improved!) system and that everyone firmly commits for accountability.
可能需要达成共识，但是无论您的团队如何做出决定，都要确保每个人都在使用新的(改进的！)系统，并且每个人都坚定地承担责任。
- Time-box the experiment and set a time for review of the newly-changed system. Calendar in a retrospective.
为实验设置时间，并设置一个时间来审查新更改的系统。 回顾中的日历。
- Rinse and repeat.
冲洗并重复。
This is a big deal for my company and me, especially since we’re in the middle of growing our team. It’s also relevant because I’ve realized that it’s high time for us to review the systems that we’ve built and, with a fine-tooth comb, take the time required to optimize and (re)build the foundation of our company.
对于我和我的公司来说，这都是一件大事，特别是因为我们正处于不断壮大的团队中 。 这也很重要，因为我已经意识到，现在是我们审查构建的系统的时候了，并且用细齿梳花费时间来优化和(重新)构建公司的基础。
How else will we ever get to the moon? ? ? ?
我们还能怎么登上月球？ ？ ？ ？
John is the software engineer at YEN, a social platform that combines the power of social networks and multiple cryptocurrency exchanges.
John 是YEN的软件工程师， YEN是一个社交平台，结合了社交网络和多种加密货币交易所的功能。
翻译自: https://www.freecodecamp.org/news/galls-law-and-what-it-has-to-do-with-startups-fd85dfbd6703/
盖尔-沙普利算法