编写代码的软件用什么编写的_如何通过像编写代码一样克服对编写的恐惧

编写代码的软件用什么编写的

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日发布。