如何在＃100DaysOfCode期间避免崩溃

by Danielle Ormshaw

丹妮尔·欧姆肖(Danielle Ormshaw)

如何在＃100DaysOfCode期间避免崩溃 (How to Avoid a Meltdown During #100DaysOfCode)

I failed my first round of #100DaysOfCode in less than 10 days.

在不到10天的时间里，我的第一轮＃100DaysOfCode失败了。

My second attempt was less calamitous, and I failed at the 50 day mark.

我的第二次尝试没有那么大的灾难，而我在50天的时间里失败了。

Alexander Kallaway designed #100DaysOfCode to break down the mental barriers to habit formation. There are plenty of success stories out there — one camper landed a job as a React developer. Why was I finding it so difficult?

亚历山大·卡洛威( Alexander Kallaway)设计了＃100DaysOfCode来打破习惯形成的心理障碍。 那里有很多成功的故事-一名露营者找到了React开发人员的工作。 为什么我觉得这么难？

I decided to perform a postmortem. As a product manager, it is my job to understand the root cause of team performance, for better or for worse. This was no different. I needed to identify and get rid of my blockers.

我决定进行验尸。 作为产品经理，了解团队绩效的根本原因是好是坏。 这没什么不同。 我需要确定并摆脱我的阻碍者。

With a degree of experimentation, I have discovered three steps that will push you to conquer #100DaysOfCode.

经过一定程度的实验，我发现了三个步骤可以促使您攻克＃100DaysOfCode。

跟踪您的动机以确定最佳的编码环境 (Track your motivation to identify your optimal coding environment)

When I started this challenge, my enthusiasm was sky high. I would drive to work an hour early, and use the extra time to code. I was smashing challenges, and having a blast sharing my progress on Twitter.

当我开始挑战时，我的热情很高。 我会提前一个小时开车去上班，并利用多余的时间进行编码。 我正在挑战，并在Twitter上分享了我的进步。

Unfortunately, the tidal wave of enthusiasm ebbed away. This moment is pivotal when forming a habit. How do you maintain momentum without the excitement?

不幸的是，热情的潮流消退了。 这是养成习惯的关键时刻。 在没有兴奋的情况下如何保持动力？

Tracking your motivation level can help you to maintain focus and clarity. The goal is to identify your triggers to low motivation. You can then design your working environment to avoid them.

跟踪您的动机水平可以帮助您保持专注和清晰。 目标是确定导致动力不足的诱因。 然后，您可以设计您的工作环境来避免这种情况。

The easiest way to track motivation is to draw a grid of 100 squares. At the end of each day, color the numbered square according to your mood. If your motivation is particularly high or low, note down why that might be.

跟踪动机的最简单方法是绘制一个100平方的网格。 每天结束时，根据您的心情给编号的方块上色。 如果您的动力过高或过低，请记下原因。

Following this method, I found that:

按照这种方法，我发现：

• My motivation to code is highest between 7:00–8:00 am
  我的编码动机是在上午7：00–8：00之间最高
• My motivation to code is lowest when I do not have a clear goal
  当我没有明确的目标时，我的编码动机最低
• Fluctuations are common when I am focused solely on tutorials
  当我只关注教程时，波动很常见

This simple exercise allowed me to adapt my habits and form a routine that suits my way of working. In this way, tracking your mood will help you to identify your optimal coding environment

这项简单的练习使我能够适应自己的习惯，并形成适合自己工作方式的日常工作。 这样，跟踪您的心情将有助于您确定最佳的编码环境

在开始挑战之前设定项目目标 (Set project goals before you start the challenge)

The first time a new coder has the confidence to say “I can build that” is both liberating, and overwhelming.

新的编码人员第一次有信心说“我可以建立那个”既解放又不知所措。

In that moment, project ideas shift away from the dream space and move toward reality. The floodgates are open, and the possibilities seem endless.

在那一刻，项目构想从梦想空间转移到现实。 水闸是敞开的，可能性似乎是无止境的。

Without a clear goal in mind, the sudden realization that you can ship working code is dangerous. In my experience, it leads to unfocused learning and constant project hopping.

如果没有明确的目标，突然意识到可以发布工作代码很危险。 以我的经验，它会导致专心的学习和不断的项目跳跃。

This scatter-gun approach is detrimental to motivation. Although you are working toward many exciting projects, you fail to make progress in any one area. At this point, you begin to feel defeated.

这种散弹枪方法不利于动力。 尽管您正在为许多激动人心的项目而努力，但是您在任何一个领域都没有取得进展。 此时，您开始感到失败。

Set realistic goals before starting #100DaysOfCode, and use them as an anchor.

在开始＃100DaysOfCode之前设置现实的目标，并将其用作锚点。

These goals can be technology based, or project based:

这些目标可以基于技术，也可以基于项目：

• What projects do I want to build in the next 100 days?
  我想在未来100天内构建哪些项目？
• What technologies do I need to understand?
  我需要了解哪些技术？
• What learning resources will help me to achieve my goals?
  哪些学习资源可以帮助我实现目标？

When you have mastered a new technology, make note of any new ideas. Acknowledge them as future projects, and continue to deliver on your original goals.

掌握了新技术后，请记下任何新想法。 将它们确认为未来的项目，并继续实现您最初的目标。

无论您失败还是成功，都可以进行项目回顾 (Whether you fail or succeed, perform a project retrospective)

The retrospective is a key ceremony in agile software development. It is an opportunity for the team to come together and reflect on their working practice. The aim is to observe what went well in this work period, and identify what must improve for the next.

回顾是敏捷软件开发中的关键仪式。 这是团队聚在一起反思自己的工作实践的机会。 目的是观察在此工作期间进展良好的情况，并确定下一个必须改进的地方。

At the end of your challenge, ask yourself the following questions:

挑战结束时，问自己以下问题：

• What did I do particularly well during this round?
  在这一回合中，我做得特别出色？
• What did I learn during the challenge session?
  在挑战赛中我学到了什么？
• What am I most proud of?
  我最引以为豪的是什么？
• What could impede my progress during future rounds?
  什么会阻碍我在以后的比赛中取得进步？

Spend some time reviewing your answers, and create a list of actions that you will take forward.

花一些时间检查您的答案，并创建将要执行的操作的列表。

I wish you the best of luck.

祝你好运。

下一步是什么？ (What’s next?)

My next round of #100DaysOfCode will begin as soon as I publish this article. You can follow my progress on Twitter.

我的下一轮＃100DaysOfCode将在我发布本文后立即开始。 您可以在Twitter上关注我的进度。

If these tips helped you to avoid a meltdown, please show your appreciation with a round of applause. Happy coding!

如果这些提示可帮助您避免崩溃，请以掌声表示感谢。 编码愉快！

翻译自: https://www.freecodecamp.org/news/how-to-avoid-a-meltdown-during-100daysofcode-5d18a3cd91b0/