27 docs tagged with "Discussion"

materials can be under the same topic or not based on the collecting perspective (as the topic), for example:

Writing backlogs can be very helpful between status transitions by:

There are three main reasons for deploying the control plane on the hosts attached to the fabric in DCs:

- Overwrite local files forcefully

People tend to name themselves and bad or good luck for their experience, but Luck is a final outcome of a person's thoughts and behaviour in a subtle way. The thoughts and behaviour are rarely noticed so luck would be the only reason for what has happened.

Making success inevitable it to ONLY do work that is incentive-based do that which you are rewarded and punished for the quality of your work do that matter to the outcomes, consequences, and results you get in life

I used to mark & highlight a lot while reading with both physical and digital books. I once thought this was a very efficient way to help me to remember, understand, and then I can quickly pick them up whenever I want, digital marking is even more convenient by bringing in highlight management and search ability.

In the video, the presenter only showed examples of L2 & L3 modelling. This is also confirmed in its paper, which states that

Two particular ways of making differentiation:

Definition

From their design purpose, some are not true at 2019:

- The most important decision is to take complete ownership of every decision in life.

系统性学习是能够客观上提高自身水平的唯一方式，所谓的系统性体现在理解相应领域的知识体系，并排除掉体系内的系列的知识盲点；而学习则不限于一般意义上的输入行为：读和听，更包含了输出以及实际练习。

In today’s fast-paced world, it’s crucial to critically evaluate any ideas, suggestions, or opinions you receive. I always ensure that the person offering advice has concrete experience in the relevant area. While general, non-practical ideas are abundant, finding someone who persistently deep-dive into a subject is much rarer and more valuable.

I’ve been encouraging taking notes to anyone who wants to seriously improve themselves, but I have to admit that the term “taking notes” is quite misleading.

Hard working is the job done with the best performance in terms of expense, time, labor, standardized and etc. Hence, for the same outcome, whoever brings more effectiveness and efficiency is working hard instead of who simply spends more time.

Targets

From result-oriented perspective, hard-working is the job done with the best performance in terms of expense, time, labor, standardized, etc. Hence, for the same outcome, whoever brings more effectiveness and efficiency is working hard instead of who simply spends more time.

Customers pay for what they have faced in lives, not average people need to do.

GTD的回顾（Review）可以按照其重要程度进行分类：

我还记得10几年前我还在大学的时候，为了解决一个编程问题可以熬通宵直到第二天中午，然后睡一觉之后吃点东西继续熬夜。毕业之后我仍然在一段时间内保持了这种熬夜的习惯，但是随着工作的时间越来越长，我几乎不在熬夜，保持早睡早起和锻炼身体。我并不认为偶尔一次全身心的投入一个问题有多大的问题，但是就长期来看我觉得这绝对不是一个好的选择——因为不管需要解决的问题是什么，以健康为代价似乎总是不合算的。

不管云平台的架构如何变化，有一点是始终不变的：虚拟主机通过网卡来发送和接收数据。这些网卡可能是用软件模拟的，或者半虚拟的。对于虚机来讲，网卡是一个很简单的设备，但它的实现方式实现思路却有很大不同。

随着前几年数据中心的火热，VXLAN也成为了一个非常热门的技术。本质上来说，它和我们常见的NVGRE类似，都是在原有的数据包外面封装一层信息，然后再套上另外一层IP信息。大概就像这样 ：

Active/Passive的灾备情况下，如果灾备中心是冷备，那么分离的3层DCI并没有多大的作用。但真正的冷备有多少呢？绝大部分有一个以上数据中心的公司都不愿意完全把第二个DC当成纯粹的备份来使用。他们可能会在备份DC上面跑跑开发或者测试，或者把负载（不平均地）分成两组，主机房跑大部分，而剩下的一部分则放到备份DC

可靠性工程师顾名思义就是保证可靠性的工程师。非常著名的《Site Reliability Engineering: How Google Runs》提到了Google内部是如何保障可靠性的。网络行业中有类似但相对小众一点的概念Network Reliability Engineer——网络可靠性工程师，当然就是保障网络稳定性的工程师。

网络架构师如同建筑行业的建筑师（架构师和建筑师的英文都是architect）一样，在理解材料、工具和操作过程中的优缺点的基础上，来实现自己心中的各种不同的设计。区别只是在使用的“原料”和“工具”不同。一个好的网络架构师必须充分理解所涉及的技术中的优缺点，并作为客户需求和技术之间的桥梁让客户的需求尽可能的成为现实。