学习 Linux 是我们的爱情语言
学习

> 
> 当一个妻子教丈夫一些新技能的时候，他们都学到了比期待更多的东西。
> 
> 
> 


![](/data/attachment/album/202003/22/163819clzuy77dc4d7q8zu.jpg)


2019 年是我们 Cherry 家学习的一年。我是一个喜欢学习新技术的高级软件工程师，并把学到的内容一起教给了我的丈夫 Chris。通过教给他一些我学到的东西，并让他全程经历我的技术演练文章，我帮助 Chris 学习到了新技术，使他能够将自己的职业生涯更深入地转向技术领域。而我学习到了新的方法，使我的演练和培训材料更易于让读者理解。


在这篇文章中，我们来讨论一下我们各自和彼此学习到了什么东西，然后探讨这对于我们的未来有何影响。


### 向学生的提问


**Jess：** Chris，是什么导致你想深入学习我的领域的技能呢？


**Chris：** 主要目的是为了让我事业更进一步。作为一个网络工程师的经历告诉我，现在的网络专家已经不像以前一样有价值了，我必须掌握更多的知识。由于网络经常被认为是造成这些天程序中断或出错的原因，我想从开发人员的角度了解更多关于编写应用程序的知识，以便于了解它们如何依赖网络资源。


**Jess：** 我首先教你什么内容？你从中学到什么？


**Chris：** 首先是从学习除此安装 Linux 系统开始的，之后又安装了 [Ansible](https://opensource.com/resources/what-ansible)。只要硬件兼容，我用过的每一个 Linux 发行版都很容易安装，但可能会出现个别不兼容的情况。这就意味着我有时候第一手学习到的是如何解决系统安装过程的最初 5 分钟出现的问题了（这个我最喜欢了）。Ansible 给了一个我学习使用软件管理器来安装程序的理由。当程序安装完成后，通过查看 yum 安装的程序，我快速了解了程序管理器是如何处理程序的依赖项的，因此，用 Python 编写的 Ansible 能够在我的系统运行。自此之后，我开始使用 Ansible 来安装各种各样的程序。


**Jessica：** 你喜欢我这种教学方式不？


**Chris：** 我们一开始有过争吵，直到我们弄清楚了我喜欢的学习方式，你也知道了应该怎样为我提供最好的学习方式。在一开始的时候，我很难跟上你讲的内容。例如，当你说“一个码头工人集装箱”的时候，我完全不知道你在讲什么。比较早的时候，我的回答就是“这是一个集装箱”，然而当时这对我来说，完全没有意义。当你对这些内容进行一些更深入的讲解后，才让学习更有趣。


**Jess：** 老实说，这对我来说也是一个重要的教训。在你之前，我从来没有教过在这个技术领域知识比我少的人，所以你帮助我认识到我需要解释更多细节。我也得说声谢谢。


当你通过这几个学习步骤的时候，你觉得我的这篇测试文章怎样呢？


**Chris：** 就我个人而言，我认为这很容易，但我错了。在我主要学习的内容中，比如你[介绍的Vagrant](https://opensource.com/resources/vagrant)，它在不同的 Linux 发行版间的变化比我想像的要多。操作系统的变化会影响设置的方式、运行都要求和特定的命令。这看起来比我用的网络设备变化更大。这让我花费更多的精力去查看这些说明是对应我的系统还是其它的系统（有时候很难知道）。在这学习路上，我似乎碰到很多问题。


**Jess：** 我每天都会遇到各种各样的问题，所以对我来说日常就是用各种方法解决各种问题。


### 向老师的提问


**Chris：** Jess，你将来教我的方式会有所改变吗？


**Jess：** 我想让你像我一样读多一些书。通过翻阅书籍来学习新技术。每天起床后一小时和睡觉前一小时我都会看书，花费一个星期左右我就能看一到两本书。我也会创建为期两周的任务计划来实践我从书本中学习到的技能。这是除了我一天中第一个小时在喝大量咖啡时读到的科技文章之外的。当我考虑到你的职业发展目标的时候，我认为除了我们谈到的优秀博客文章和文章之外，书籍是一个重要的元素。我觉得我的阅读量使我保持进步，如果你也这么做了，你也会很快赶上我的。


**Chris：** 那么学生有没有教过老师呢？


**Jess：** 我在你那里学习到耐心。举个例子，当你完成了安装 Ansible 的时候，我问你下一步要怎样操作的时候。你直接回复我，“不知道”，这不是我想让你学习到的内容。所以我改变了策略，现在在逐步安装任何组件之前，我们将详细讨论你想要实现的目标。当我们在写 Vagrant 文章的时候，我们一起进行相应的演示操作，我以创建它时就牢记目标，因此我们就有一些需要马上实现的目标。


这实际上对我在工作中的培训方式产生了巨大的改变。现在我在大家学习的过程中会问更多问题，并更多地进行手把手讲解。我更愿意坐下来仔细检查，确保有人明白我在说什么和我们在做什么。这是我之前从来没有做过的。


### 我们一起学到了什么


做为一对夫妇，在这一年的技术合作中我们的技术都有所增长。


**Chris：** 我对自己学到的东西感到震惊。通过一年课程学习，我认识了新操作系统、如何使用 API、使用 Ansible 部署 Web 应用和使用 Vagrant 启动虚拟机器。我还学习到了文档可以让生活变得更好，所以我也会尝试去写一写。然而，在这个工作领域，操作并不总是被记录在案，所以我学会了准备好处理棘手的问题，并记录如何解决它们。


**Jess：** 除了我在教你中学到的知识外，我还专注于学习 Kubernetes 在云环境中的应用知识。这包括部署策略、Kubernetes API 的复杂度、创建我自己的容器，并对环境进行加密处理。我还节省了探索的时间：研究了 serverless 的代码、AI 模型、Python 和以图形方式显示热图。对于我来说，这一年也很充足。


我们下一个目标是什么？现在还不知道，但我可以向你保证，我们将会继续进行分享它。




---


via: <https://opensource.com/article/20/2/linux-love-language>


作者：[Christopher Cherry](https://opensource.com/users/chcherry) 选题：[lujun9972](https://github.com/lujun9972) 译者：[sndnvaps](https://github.com/sndnvaps) 校对：[wxy](https://github.com/wxy)


本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出


OK
2019 was a year of learning in the Cherry household. I am a senior software engineer who set out to learn new skills and, along the way, I taught my husband, Chris. By teaching him some of the things I learned and asking him to work through my technology walkthrough articles, I helped Chris learn new skills that enabled him to pivot his career deeper into the technology field. And I learned new ways to make my walkthroughs and training materials more accessible for readers to digest.

In this article, we talk about what we learned individually and from each other, then we explore what it means for their future.

## Questions for the student

**Jess:** Chris, what made you want to learn more about my field?

**Chris:** It was primarily to further my career. Being in network engineering has shown me that being an expert only on networks is not as valuable as it once was, and I have to know a little bit of everything. Since the network is often blamed for outages or application challenges these days, I wanted to understand more from a developer's perspective on writing applications so I could see how they depend on the network as a resource.

**Jess:** What did I teach you first, and what did you learn from it?

**Chris:** It all started with installing Linux for the first time, then adding [Ansible](https://opensource.com/resources/what-ansible). Each Linux distribution I worked with was easy enough to install, as long as the hardware was compatible, but compatibility wasn't always clear. That meant sometimes I learned first-hand how to troubleshoot Linux within the first five minutes of running an installation (and I liked it). Ansible gave me a reason to learn Linux package managers to install the software. Once it was installed, I quickly learned how package management handles dependencies as I looked at the files that yum installed, so Ansible, which is written in Python, can run on my system. From there, I started to install all kinds of applications with Ansible.

**Jessica:** Do you like the way I taught you?

**Chris:** We had our struggles at first, until we ironed out how I like to learn and how you should present the best way for me to learn. In the beginning, it was hard to follow what you meant. For instance, when you said things like "a Docker container," I had no reference to what you were talking about. Early on, the response was, "well, it's a container," which meant nothing to me at the time. Once I got you to explain it in more detail, it became a lot more fun to learn.

**Jess:** To be fair, this was a big lesson for me as well. I hadn't trained anyone with less knowledge on this technology than me before you, so you helped me realize that I needed to be clearer with my explanations. Thanks for that.

How did you feel about testing my articles, the ones where I had you run through the steps?

**Chris:** Personally, I thought it would be easy, and boy, was I wrong. One of the main things I learned from these, like your [introduction to Vagrant](https://opensource.com/resources/vagrant), was how each Linux distribution varies more than I realized. The operating system (OS) changes how you set it up, the requirements to run, and the specific commands. It seems like a lot more variability than there is with the network gear I've worked on. So I started to pay a lot more attention to the instructions and whether they were written for my OS or another one (and how difficult it can be to know sometimes). I seemed to break a lot of things along the way.

**Jess:** I break stuff all day, so different paths for different problems are daily occurrences for me.

## Questions for the teacher

**Chris:** Jess, would you change anything with the way you taught me so far?

**Jess:** I'd have liked to make you read more, as I do. Learning new technology has me churning through books. I read a book and a half, if not two books, a week, and that's with spending one hour in the morning and one hour before bed every day. I also pick one project to run through for two weeks for about an hour a day to reinforce the book skills. And that's in addition to the tech articles I read for the first hour of my day while taking in an immense amount of coffee. When I think about your goal to grow your career, I think books are an important element alongside the great blog posts and articles we talk about. I feel my reading regiment has kept me up to speed, and if you did the same, you would catch up to me pretty quickly.

**Chris:** So did the student teach the teacher in any way?


**Jess:** I learned a great deal about being patient from you. For instance, after walking through an installation of Ansible, I asked what you wanted to do next. Your first answer was, "I don't know," which was hard for me because I want you to learn what you want to learn. So I changed my approach, and now we talk more about what you want to achieve before walking through installing anything. When we moved on to the Vagrant article we worked on together, I created it with an end goal in mind, so we had something to achieve right away.

This actually made a massive change in how I do training at work. Now I ask more questions on how people learn and work hand-in-hand more often than I did before. I am more likely to sit and go through and make sure someone understands what I'm saying and what we're doing. I wasn't really before.

## What we learned together

As a couple, we both grew from collaborating on technology over the last year.

**Chris:** I'm blown away at how much I learned. Over the course of a year, I understand new operating systems, how to use an API, web application deployment with Ansible, and standing up virtual machines with Vagrant. I also learned how documentation makes life better, so it's worth the time it takes to write some. In this field of work, however, behavior isn't always documented, so I've learned to be ready to work through tough issues and document how I fix them.

**Jess:** Beyond what I learned from teaching you, I've focused on learning a good deal about Kubernetes in cloud environments. That includes deployment strategies, the complexity of the Kubernetes API, building my own containers, and securing these environments. I've also saved time to dabble: toying around with serverless code, AI models, Python, and graphically displaying heat maps. It's been a good year.

What's next for us? It's yet to be seen, but I can assure you that we're going to share it here on Opensource.com.

**Who did you mentor in 2019, or who are you mentoring in 2020? Tell us about it in the comments.**

## 2 Comments