驗證曲線和學習曲線

Doing what I do for a living, which these days mostly involves creating technology books and courseware, I’m constantly learning new technologies. In a way, my new tech adventures are not much different than the ones most IT pros face, except that mine probably hit more often.

做我自己的工作，這些日子主要涉及創建技術書籍和課件 ，我一直在學習新技術。 從某種意義上說，我的新技術歷險與大多數IT專業人員所面臨的冒險并沒有太大不同，只是我的新技術冒險命中率更高。

Because there’s so much depending on my understanding the new platform or process?—?and so many other newer platforms and processes waiting for my attention once I’m done with this one?—?my primary goal is to get in and out as fast as possible.

因為在很大程度上取決于我對新平臺或流程的理解-以及許多其他較新的平臺和流程在我完成這一工作后等待我的注意-我的主要目標是盡可能快地進出。

Trying to organize the layers of complexity and design metaphors inherent in a technology while struggling to figure out if it’ll even do exactly what I want can sometimes be downright intimidating. Without a good plan of attack, I’m dead in the water.

試圖組織技術固有的復雜性和設計隱喻的層級，同時努力弄清楚它是否能夠完全滿足我的要求，有時可能會令人生畏。 沒有好的進攻計劃，我就死定了。

Before I share a couple of the tools that I’ve used successfully in my own learning, it’s worth discussing a real-world (relatively) new technology.

在分享自己在學習中成功使用的兩個工具之前，有必要討論一下現實世界(相對)的新技術。

A while back, the operations management monitoring company ScienceLogic conducted a survey of more than a thousand enterprise and IT professionals, seeking their thoughts on cloud adoption. While it’s clear that more and more of the IT workload is shifting to cloud providers (with Amazon Web Services leading the way by every metric), there’s deep and widespread concern over what the impact of the change might be.

不久前，運營管理監控公司ScienceLogic 對一千多名企業和IT專業人員進行了調查 ，以征詢他們對云采用的想法。 顯然，越來越多的IT工作負載正在轉移到云提供商(Amazon Web Services在每個指標方面都處于領先地位)，但人們對這種變化的影響深表憂慮。

31% of respondents felt they lacked the skills to confidently lead a cloud deployment, 50% claimed they lacked the tools to properly manage infrastructure in the cloud, and 28% worried that the shift to the cloud could endanger their current jobs.

31％的受訪者認為他們缺乏自信地領導云部署的技能，50％的受訪者表示他們缺乏適當管理云中基礎架構的工具，還有28％的受訪者擔心向云的轉變可能會危及當前的工作。

Sound familiar? The faster and more disruptive the change, the more we all worry about how?—?or if?—?we’ll keep up. And if you think Joe IT Professional stays up nights wondering how he’ll figure it all out, show some sympathy for his manager who’s responsible for dragging an entire department into the cloud.

聽起來有點熟？ 變更越快，破壞性越大，我們所有人就越會擔心如何(或是否)能夠跟上進展。 而且，如果您認為Joe IT Professional徹夜難眠，想知道他將如何解決所有問題，請對負責將整個部門拖到云中的經理表示同情。

AWS in particular is on my mind right now because my Wiley/Sybex book “AWS Certified Cloud Practitioner Study Guide” just came out. AWS was a technology I first struggled to understand more than a decade ago when I needed to build my own public-facing web conferencing system (using BigBlueButton). It was a long journey between that first EC2 server and the comfort level and deep experience I reached before attempting the book, but the things I got right?—?and wrong?—?while taking those first steps went a long way to shape how I now teach IT topics.

由于我的Wiley / Sybex書“ AWS認證的云實踐者學習指南 ”剛剛出版，因此我現在特別想到AWS 。 AWS是十多年前我第一次努力了解的技術，當時我需要構建自己的面向公眾的Web會議系統(使用BigBlueButton)。 從第一臺EC2服務器到嘗試本書之前達到的舒適度和深厚的經驗之間的漫長旅程，但是，我采取的第一步的正確與錯誤之道對我現在教授IT的方式有很大幫助。主題。

順序與掃描和運行 (Sequential vs scan-and-run)

How you’ll learn a skill partly depends on what you’re planning to learn. If you’re looking for an introduction that will take you from zero to functional on a full-stack, multi-tier environment like AWS, then you might be safer going sequential. Starting at the beginning can help you avoid missing critical details?—?like the way billing or security work on AWS. Trust me: if you don’t like the idea of surprise four-digit monthly service charges or compromised infrastructure, then you don’t want to skip the billing and security basics.

您如何學習某種技能部分取決于您計劃學習的內容。 如果您正在尋找可以使您從零開始在全棧，多層環境(例如AWS)上正常運行的介紹，那么順序執行可能會更安全。 從一開始就可以幫助您避免丟失關鍵細節，例如AWS上的計費或安全性工作方式。 相信我：如果您不喜歡每月四位數的服務費或基礎設施受損的想法，那么您就不想跳過計費和安全性基礎知識。

But if it’s a standalone software package (like a virtualization technology or a new IDE) that you can safely test a few times in your own network before actually deploying for real, then fasterer is gooderer. For this kind of project I will often fire up a clean Linux container using LXC (which, for exploring new software, I find far preferable to Docker) or, when the application I’m working with requires host kernel access (like SELinux), a Linux virtual machine on Virtual Box.

但是，如果它是一個獨立的軟件包(例如虛擬化技術或新的IDE)，則可以在實際部署之前在自己的網絡中安全地測試幾次，然后越快越好。 對于此類項目，我通常會使用LXC來啟動一個干凈的Linux容器(為了探索新軟件，我發現它比Docker更可取)，或者當我使用的應用程序需要主機內核訪問權限時(例如SELinux)， Virtual Box上的Linux虛擬機 。

By “scan-and-run” I mean carefully crafting a search string in DuckDuckGo.com (or one of those other search engines whose names escape me at the moment), quickly picking out the information you want from the results, and trying it on your disposable virtual server. Didn’t work? Congrats. You’ve just learned something you didn’t yet know.

“掃描并運行”的意思是在DuckDuckGo.com(或其他目前名稱不為人知的搜索引擎之一)中精心設計搜索字符串，快速從結果中挑選出所需信息，然后進行嘗試在您的一次性虛擬服務器上。 沒工作嗎 恭喜。 您剛剛學到了一些您還不知道的東西。

Just make sure to properly document both your failures and successes so you don’t have to walk around the same park over and over again.

只需確保正確記錄您的失敗和成功，即可避免一遍又一遍地走在同一個公園里。

命令行 (The command line)

Given a choice, I generally prefer working from the Bash command line over GUI consoles. It’s not because I’m a command line snob (although I am), but I find the unambiguous and trackable nature of a CLI works well with iterative experiments. In plain language, that means it’s easier to retrace my steps to figure out exactly what worked and what didn’t. And don’t forget that Bash error messages can easily be recycled into terrific internet searches.

如果有選擇，我通常更喜歡從Bash命令行而不是GUI控制臺進行工作。 這不是因為我是命令行勢利小人(盡管我是)，但我發現CLI的明確性和可追蹤性在迭代實驗中很好地起作用。 用通俗易懂的語言，這意味著更容易地追溯我的步驟，以準確地找出哪些有效，哪些無效。 并且不要忘記，Bash錯誤消息可以輕松地回收到出色的Internet搜索中。

Another CLI advantage: the predictable patterns of a well-designed shell environment can make it even easier to anticipate functionality than a well-designed web GUI. Let me illustrate that using the AWS CLI. Once it’s installed and properly configured, even running `aws` without any arguments will get you something useful. Notice how the output guides you to add `help` to any partially completed command to return contextual assistance.

CLI的另一個優點是：精心設計的shell環境的可預測模式可以使設計功能比精心設計的Web GUI更加容易。 讓我使用AWS CLI進行說明。 一旦安裝并正確配置它，即使運行不帶任何參數的“ aws”也會為您帶來一些幫助。 注意輸出如何引導您將“ help”添加到任何部分完成的命令中以返回上下文幫助。

$ aws

$ aws

$ awsusage: aws [options] <command> <subcommand> [<subcommand> …] [parameters]

$ aws 用法：aws [選項] <命令> <子命令> [<子命令>…] [參數]

$ awsusage: aws [options] <command> <subcommand> [<subcommand> …] [parameters]To see help text, you can run:

$ aws 用法：aws [選項] <命令> <子命令> [<子命令>…] [參數] 要查看幫助文本，可以運行：

aws help

AWS幫助

aws help aws <command> help

aws help aws <命令>幫助

aws help aws <command> help aws <command> <subcommand> help

aws幫助 aws <命令>幫助 aws <命令> <子命令>幫助

aws help aws <command> help aws <command> <subcommand> helpaws: error: too few arguments

aws幫助 aws <命令>幫助 aws <命令> <子命令>幫助 aws：錯誤：參數太少

It’s true that there’s plenty of help available through the GUI: all AWS console pages have links to extensive documentation resources. But that would be AWS documentation which, while well written and carefully maintained, is usually very, very wordy and sometimes a bit confusing. The inline CLI docs are much more focused and get you in and out more quickly.

的確，通過GUI提供了很多幫助：所有AWS控制臺頁面都有指向大量文檔資源的鏈接。 但這將是AWS文檔，盡管編寫得當且經過精心維護，但它們通常非常冗長，有時會造成混淆。 內聯CLI文檔更加集中，可讓您更快地進入和退出。

Just being familiar with how to access this kind of information can make you much faster and more effective…even through the early learning stages. And the basic structure is available far beyond just AWS.

只要熟悉如何訪問此類信息，就可以使您更快，更有效……甚至在早期學習階段也是如此。 而且基本結構遠不止AWS。

On the other hand, as I wrote in my "Learn AWS in a Month of Lunches" book, I feel that the AWS browser console is actually a better place to first come to grips with the workings of Amazon’s cloud. That’s because high-level structure plays such a large role in understanding the way the dozens and dozens of AWS services work together, and the website does such a good job visualizing it. But maybe that’s just me.

另一方面，正如我在“在一個月的午餐中學習AWS”一書中所寫的那樣，我認為AWS瀏覽器控制臺實際上是一個更好地掌握Amazon云工作原理的好地方。 這是因為高層結構在理解數十個AWS服務一起工作的方式中起著很大的作用，并且網站在可視化方面做得很好。 但是也許就是我。

自己做 (Do it yourself)

More than anything else, your learning will be the most effective if you roll up your sleeves and try it out. Not only should you duplicate the documentation examples, but change the parameters around to see what breaks. And then plan and execute your own projects based on the technologies you’re learning. Applying your knowledge to the real world is critical.

最重要的是，如果您袖手旁觀并嘗試一下，那么學習將是最有效的。 您不僅應該復制文檔示例，而且還可以更改參數以查看有什么問題。 然后根據要學習的技術計劃并執行自己的項目。 將您的知識應用于現實世界至關重要。

翻譯自: https://www.freecodecamp.org/news/beating-the-technology-learning-curve-monster/

驗證曲線和學習曲線