編寫代碼的軟件用什么編寫的

by Chris Rowe

通過克里斯·羅

How often do you get the fear? What do I mean by fear? How about the knot I got in my stomach just before I plunged out of plane on a parachute jump? It’s more than the brain logically planning to avoid danger, your whole body feels it, a foreboding about what’s coming next.

您多久得到一次恐懼？ 恐懼是什么意思？ 在降落傘跳下從飛機上跳下之前，我的肚子里的結怎么樣？ 整個身體都感覺到，這不僅僅是大腦在邏輯上規避危險的計劃，對即將發生的事情的預感。

Working in IT means sudden severe physical dangers are unlikely. But aversion to fear continues to exist when we get asked to do certain tasks.

在IT部門工作意味著不太可能出現嚴重的物理危險。 但是當我們被要求去做某些任務時，對恐懼的厭惡仍然存在。

In my first job, it was when my boss asked me “Have you completed the documentation?”

在我的第一份工作中，就是老板問我“您是否完成了文檔？”

In my 2nd job it was “Did you send that email to the customer yet?”

在我的第二份工作中，是“您是否已將該電子郵件發送給客戶？”

And later “How’s that presentation going?”

然后是“演示文稿進行得怎么樣？”

What was the problem? All those tasks involved writing. It couldn’t get much worse than that. Very few developers like writing (unless it’s in Slack). The bigger the audience and the more important it is, the more fear the writing task brings.

怎么了 所有這些任務都涉及寫作。 沒有比這更糟糕的了。 很少有開發人員喜歡編寫代碼(除非它在Slack中 )。 受眾越多，重要性越高，寫作任務帶來的恐懼就越大。

Back to coding. When was the last time your code worked the first time? The time you wrote a couple of hundred lines of code that were error free and to perfection, so that it compiled and ran exactly as expected the first time?

回到編碼。 您的代碼上次上次工作是什么時候？ 您編寫幾百行無誤且完美的代碼，以便它第一次編譯和運行完全符合您的預期嗎？

We as developers would never expect first time code perfection, and coding is our main task. Yet when asked to write some documentation, an important customer email, or a presentation, we freeze. The empty coffee cups and Fritz Cola bottles pile up on the desk while we’re staring at a blank page, waiting for the perfect text to flow out from us.

作為開發人員，我們永遠不會期望首次代碼完美，而編碼是我們的主要任務。 但是，當被要求寫一些文檔，重要的客戶電子郵件或演示文稿時， 我們凍結了 。 當我們盯著空白頁時，空的咖啡杯和弗里茨可樂瓶堆積在桌子上，等待完美的文字從我們中間流出。

This doesn’t make much sense. Could it be that our expectations for a side task that we often don’t like are higher than for the core task that we love and practice all the time?

這沒有多大意義。 難道我們對我們經常不喜歡的副業的期望比對我們一直熱愛和實踐的核心任務的期望高嗎？

Writing and coding have a lot more in common than you might think. And surprisingly you can use your coding skills to improve your writing.

編寫和編碼的共同點比您想象的要多得多。 令人驚訝的是，您可以利用您的編碼技能來改善寫作。

As developers, we’re usually keen to jump straight into coding as quickly as possible. We don’t want to think the code through to perfection in our heads. We want to try out and experiment. We want to get a result. Once we’ve got the basics sorted then we can expand and refine our work. So much so that we’ve got terminology and methodologies to back this up. Think Scrum or refactoring.

作為開發人員，我們通常希望盡快進入編碼。 我們不想將代碼徹底考慮進去。 我們想嘗試一下。 我們想要得到結果。 整理好基礎知識之后，我們就可以擴展和完善我們的工作。 如此之多，以至于我們有了術語和方法來支持這一點。 考慮使用Scrum還是重構 。

Scrum is a framework based on getting something out there and improving it. It was created to move away from the unrealistic expectations of the waterfall methodology. Where you can theoretically completely define everything that you need to do before you start doing it.

Scrum是一個框架，它基于從那里得到一些東西并對其進行改進。 它的創建是為了擺脫瀑布方法學的不切實際的期望。 從理論上講，您可以在其中完全定義開始做之前需要做的所有事情。

With Scrum, the idea is inspect and adapt. Perfection is never the aim of the first sprint. Get the most important thing out in the open so it can be refined and added to later.

使用Scrum的想法是檢查和適應。 完美絕不是第一次沖刺的目的。 公開獲取最重要的信息，以便對其進行完善和添加。

[Refactoring] advantages include improved code readability and reduced complexity (Wikipedia)

[重構]的優勢包括改進的代碼可讀性和降低的復雜性( Wikipedia)

With code, the first version is not expected to be perfect. It’s about getting the initial version out and then improving it afterwards to make it easier to read and simpler.

使用代碼，第一個版本預計不會是完美的。 它是要發布初始版本，然后對其進行改進，以使其更易于閱讀和簡化。

您可以編輯空白頁嗎？ (Can you edit a blank page?)

But what happens when you switch your favorite coding IDE for an email editor or PowerPoint? I’ve seen countless developers freeze with fear, staring at a blank screen. Unsure what to write, worried it won’t be perfect and so we write nothing. You can sense the fear when your co-workers have it, it’s the constant sighing and nervous energy of tapping fingers.

但是，當您將自己喜歡的編碼IDE切換為電子郵件編輯器或PowerPoint時，會發生什么？ 我已經看到無數開發人員因恐懼而凝視著黑屏。 不確定該寫些什么，擔心它不會是完美的，所以我們什么也沒寫。 當您的同事感到恐懼時，您就可以感覺到恐懼，這是敲擊手指不斷產生的嘆息和緊張感。

But if we’re honest with ourselves this “perfection or nothing” is the exact opposite to the coding approach that we spend all day practicing. If it was coding we’d be happy to try some of the simple cases and get it up and running. Not for writing. Perhaps it’s because we’re worried about our clarity, structure, or style. And this all before we’ve even got any words the page.

但是，如果我們對自己誠實，那么“完美或一無所有”與我們一整天都在練習的編碼方法完全相反。 如果是編碼，我們很樂意嘗試一些簡單的案例并使其啟動并運行。 不適合寫作。 也許是因為我們擔心我們的清晰度，結構或樣式。 而在此之前，我們甚至還沒有對頁面進行任何說明。

Waiting for the perfect words to form in our heads so we can just write them down is never going to happen. It doesn’t happen with coding so why do we expect it with writing.

等待完美的單詞在我們腦海中形成，以便我們可以將它們寫下來，這永遠不會發生。 編碼不會發生這種情況，所以我們為什么要在編寫時期望它。

Switching contexts can show this. Have you ever tried to refactor a program that’s zero lines long? So why are you trying to do that when it comes to documentation, email or a presentation. I like this quote from Jodi Picoult…

切換上下文可以顯示這一點。 您是否曾經嘗試過重構零行程序？ 因此，當涉及到文檔，電子郵件或演示文稿時，為什么要嘗試這樣做。 我喜歡Jodi Picoult的這句話……

You can always edit a bad page. You can’t edit a blank page.

您始終可以編輯錯誤的頁面。 您無法編輯空白頁。

You have to actually get something down on the page before you can improve it. In Marion Smith’s book she refers to this as “vomiting” the first draft. Anne Lamott calls it the “sh*tty first draft”. One thing is clear. The first draft is not going to be pretty, but it’s the necessary first step.

您必須先在頁面上找到一些內容，然后才能加以改進。 在馬里恩·史密斯(Marion Smith)的書中，她將其稱為“嘔吐”初稿。 安妮·拉莫特(Anne Lamott)稱其為“噓*初稿”。 一件事很清楚。 初稿不會很漂亮，但這是必要的第一步。

Feel the weight lifting off your shoulders as you give yourself permission to write the first thing that comes to mind, regardless of the quality. With coding you want the first version to do something OK. With writing you just need to get some words on the page. Any words. There’s no compiler to reject them so what are you worrying about?

不管質量如何，在您允許自己編寫想到的第一件事時，都可以感覺到肩膀上的重量減輕了。 使用編碼，您希望第一個版本執行某些操作。 通過寫作，您只需要在頁面上寫下一些文字即可。 任何話 沒有編譯器拒絕它們，所以您擔心什么？

摘要 (Summary)

Getting a minor dose of fear before you start writing is normal. It happens to professional writers so it’s not surprising that it also happens to developers when they need to write.

在開始寫作之前得到一點恐懼是正常的。 它發生在專業作家身上，所以當開發人員需要寫作時也發生這種情況也就不足為奇了。

My recommendations are:

我的建議是：

• Get something on paper, anything at all. Write down whatever comes into your head.
  拿紙上的東西，什么都沒有。 寫下您腦海中的一切。
• Use agile/Scrum rules: iterate and adapt
  使用敏捷/ Scrum規則：迭代和適應
• Use coding refactoring rules: reduce complexity and improve readability over time
  使用編碼重構規則：隨著時間的流逝降低復雜性并提高可讀性

Just remember, the next time your boss asks “Have you sent that customer email out?” you’re not doing a parachute jump. All you need to overcome your fear is to vomit out your first draft and iterate.

請記住，下次您的老板問“您是否已發送該客戶電子郵件？” 你不是在跳傘。 克服恐懼所需要做的就是嘔吐初稿并進行迭代。

You already have the coding skills, now you just have to apply them to your writing.

您已經具備編碼技能，現在只需要將其應用于寫作即可。

Originally published by Chris Rowe at leadtechie.com on March 3, 2019.

最初由克里斯·羅(Chris Rowe)在Leadtechie.com于2019年3月3日發布。

翻譯自: https://www.freecodecamp.org/news/how-to-overcome-your-fear-of-writing-by-writing-like-you-code-d0d6edb9ff62/

編寫代碼的軟件用什么編寫的

總結

以上是生活随笔為你收集整理的编写代码的软件用什么编写的_如何通过像编写代码一样克服对编写的恐惧的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。