A lot of people haven't heard bus number before, which I find immensely useful. Once someone has it explained to them, I've noticed they really get a kick out of it and see the utility of such a concept immediately.
For those of you on SO who haven't heard it before, the bus number of a project or undertaking is the minimum number of people who, if they were to be hit by a bus, would cause the project to fail or place it in jeopardy of failure. Whenever a person holds too much institutional or technical knowledge on a project, the bus number becomes 1, meaning that if this person is unavailable, the project is likely to fail. (You might say such a person is an information silo, which is another useful term.)
Your goal is to have the bus number be close to the size of the entire team (that is, a good chunk of the team has to be out of commission before there's a serious risk of failure).
Note that a low bus number isn't bad, per se. It may be that you have team members with incredibly specialized knowledge that would take too long to transfer to someone else. But it's a warning sign that you have a risk which will be difficult to mitigate: you can't merely hire someone else to replace the person, nor can you ask that person to educate other team members without sacrificing at least some of their effectiveness and temporarily slowing progress.
If you encounter jargon in an interview, stop and ask the interviewer to explain what they mean. This gives the interviewer a much better impression that you're honest and interested in learning than trying to stumble through the interview.
Start a technical jargon file. When you encounter things like "technical debt" at work, on blogs or whatever, add it to your jargon file. Google it and get a sense of its meaning.
When you're done with step two, post an answer here :)
The only other term I know which makes a financial analogy like "technical debt", is "software taxes": work that needs doing, but brings no immediate benefit, such as internationalization (or i18n).
There are probably thousands of obscure specialized terms, by language (hygienic macros?), application domain (rapid time?), business domain (any number of TLAs), company culture (microsoftese), or historical heritage.
In interviews, it's much better to admit that you do not know what a specialized term means than to give an inexact answer about something you do not really know about.
Interview questions are usually a way for the interviewer to get a feel of your personality, the answers you give are not really essential.
发布评论
评论（3）
很多人以前没有听说过公交车号码，我发现这非常有用。一旦有人向他们解释了这个概念，我注意到他们真的很喜欢这个概念，并立即看到了这个概念的实用性。
对于那些以前没有听说过 SO 的人来说，项目或事业的巴士号码是如果被巴士撞到，将导致项目失败或的最小人数。使其面临失败的危险。每当一个人在一个项目上拥有太多的制度或技术知识时，总线编号就会变成1，这意味着如果这个人不可用，该项目很可能会失败。 （您可能会说这样的人是信息孤岛，这是另一个有用的术语。）
您的目标是让公交车数量接近整个团队的规模（即，一个很好的块）在出现严重失败风险之前，团队的成员必须停止运行）。
请注意，总线数量少本身并不是坏事。您的团队成员可能拥有极其专业的知识，而将这些知识转移给其他人需要很长时间。但这是一个警告信号，表明您面临着难以减轻的风险：您不能仅仅雇用其他人来代替该人，也不能要求该人在不牺牲至少部分效率的情况下教育其他团队成员，并且暂时减缓进度。
A lot of people haven't heard bus number before, which I find immensely useful. Once someone has it explained to them, I've noticed they really get a kick out of it and see the utility of such a concept immediately.
For those of you on SO who haven't heard it before, the bus number of a project or undertaking is the minimum number of people who, if they were to be hit by a bus, would cause the project to fail or place it in jeopardy of failure. Whenever a person holds too much institutional or technical knowledge on a project, the bus number becomes 1, meaning that if this person is unavailable, the project is likely to fail. (You might say such a person is an information silo, which is another useful term.)
Your goal is to have the bus number be close to the size of the entire team (that is, a good chunk of the team has to be out of commission before there's a serious risk of failure).
Note that a low bus number isn't bad, per se. It may be that you have team members with incredibly specialized knowledge that would take too long to transfer to someone else. But it's a warning sign that you have a risk which will be difficult to mitigate: you can't merely hire someone else to replace the person, nor can you ask that person to educate other team members without sacrificing at least some of their effectiveness and temporarily slowing progress.
我认为你应该做两件事：
完成第二步后，请在此处发布答案:)
I think you should do two things:
When you're done with step two, post an answer here :)
我所知道的唯一一个与“技术债务”类似的财务类比的术语是“软件税”：需要做的工作，但不会立即带来好处，例如国际化（或 i18n）。
根据语言（卫生宏？）、应用程序领域（快速时间？）、业务领域（任意数量的 TLA）、公司文化（微软语）或历史遗产，可能有数千个晦涩的专业术语。
在面试中，承认你不知道某个专业术语的含义比对你并不真正了解的事情给出不准确的答案要好得多。
面试问题通常是面试官了解你性格的一种方式，你给出的答案并不重要。
The only other term I know which makes a financial analogy like "technical debt", is "software taxes": work that needs doing, but brings no immediate benefit, such as internationalization (or i18n).
There are probably thousands of obscure specialized terms, by language (hygienic macros?), application domain (rapid time?), business domain (any number of TLAs), company culture (microsoftese), or historical heritage.
In interviews, it's much better to admit that you do not know what a specialized term means than to give an inexact answer about something you do not really know about.
Interview questions are usually a way for the interviewer to get a feel of your personality, the answers you give are not really essential.