游泳后精疲力尽

by Ryan Yurkanin

瑞安·尤卡宁(Ryan Yurkanin)

精疲力尽的编程后如何重回正轨 (How to get back on track after you’ve burned out programming)

Our brains can only take so much. We’ve all had to handle a problem so complex it broke us. We’ve all felt like imposters at our jobs when something just wouldn’t click.

我们的大脑只能花那么多。 我们所有人都必须处理一个如此复杂的问题，使我们不堪重负。 当某些事情根本无法点击时，我们所有人都觉得自己是骗子 。

This all makes us frustrated and angry, so our code becomes worse. Our code being worse makes us more upset. We are now in a cycle of self-loathing and dev tears.

这一切都使我们感到沮丧和愤怒，因此我们的代码变得更糟。 我们的代码更糟使我们更加沮丧。 我们现在处于自我厌恶和开发者泪水的循环中。

哪里出错了？ (Where did it all go wrong?)

Some would say that problems are just going to be hard, and you need to do one of the following:

有人会说问题将变得很棘手，您需要执行以下一项操作：

1. Give up and find an easier problem. (If only) ?
   放弃并找到一个更简单的问题。 (要是) ？
2. Become smarter and better at our job. (This definitely won’t lead to crippling depression and anxiety) ?
   在我们的工作中变得更聪明，更好。 (这绝对不会导致严重的抑郁和焦虑)？

Yeah so, those options suck. If we’re really struggling with code, I don’t think the most therapeutic solution is to code more.

是的，这些选择很烂 。 如果我们真的在代码方面苦苦挣扎，我认为最有效的解决方案不是编写更多代码。

Do you have to remind yourself every 5 minutes of the code style guide that lives in your lead developer’s head?

您是否需要每隔5分钟提醒您一次出现在首席开发人员头脑中的代码样式指南？

Did you have an hour long argument with a coworker about the space complexity of your React code?

您是否与同事争论了一个小时，涉及您的React代码的空间复杂性？

What can we actually do to improve our workflow?

我们实际上可以做些什么来改善工作流程？

Let’s talk through some non-programming ways to make us better programmers. Opinions ahead, pick what works for you and your team.

让我们来谈谈一些非编程方式，以使我们成为更好的程序员。 提前发表意见，选择对您和您的团队有用的方法。

您应该得到快乐，所以找到让您快乐的因素并做更多的事情 (You deserve to be happy, so find what makes you happy and do it more)

Okay, so this one seems like it should be a no brainer, but is it? Let me repeat that: you deserve to be happy. Stop programming, and do what you love more. I promise when you come back not only will you code better, but your mood will influence your coworkers as well.

好的，所以这似乎应该是毫无道理的，但是吗？ 让我重复一遍：你应该开心。 停止编程，做自己喜欢做的​​事。 我保证，当您回来时，不仅代码会更好，而且您的心情也会影响您的同事。

When you’re in a good state of mind, it’s easier to pick your battles. You’ll be more likely to let the little things slide, and you’ll be harder to bring down.

当您处于良好状态时，选择战斗就更容易了。 您将更容易让小事情滑落，并且您将更难以降低。

可以自动化所有样式指南规则。 警惕那些你做不到的人。 (Automate all the style guide rules you can. Be wary of those you can’t.)

Solving a core problem is hard enough. The last thing you need is to disrupt your line of thought every 5 minutes over whether you need a semicolon or not.

解决核心问题已经足够困难。 您需要做的最后一件事是每5分钟中断一次是否需要分号的思路。

Look for tools like Prettier and ESLint, and use common configurations found online. There are some sick benefits here:

查找类似Prettier和ESLint的工具，并使用在线找到的常见配置。 这里有一些病假福利：

1. If a coworker hates a rule, there’s no one on the team to confront. You can shake your fists together at whoever came up with the common ruleset.

   如果同事讨厌规则，那么团队中就没有人要面对。 您可以在一起谁与共同的规则集上来动摇你的拳头。

2. You can have auto fix on save in most editors, so no more fixing code by hand! Mash save and focus on what matters!
   您可以在大多数编辑器中保存时自动修复，因此不再需要手工修复代码！ 节省现金并专注于重要事项！
3. You can set up automated checks when someone submits a PR, reducing nitpick overhead.
   您可以在有人提交PR时设置自动检查，从而减少nitpick开销。

问问自己“如果我放手，会发生什么？” (Ask yourself “If I just let this go, what will happen?”)

If there is one thing that I’m guilty of, it’s arguing about stuff that doesn’t make a huge difference at the end of the day.

如果有一件我有罪的事情，那就是在争论那些最终并没有太大改变的事情。

I prefer premature optimization of my coworker’s mental health over computer memory.

与计算机内存相比，我更喜欢过早优化同事的心理健康。

Computer’s are getting bigger and faster every year, while human’s can only take so much.

每年，计算机的体积越来越大，速度越来越快，而人类的体积却越来越大。

Understanding what you might get out of winning an argument is important. On one hand, you may save heap space, on the other, you may ruin your coworker’s day and that negativity will ripple out.

了解您从争吵中可能得到的收获很重要。 一方面，您可以节省堆空间，另一方面，您可能会破坏同事的工作，并且消极情绪会泛滥成灾。

Of course there are times when you need to value the code and performance. That’s when you’ll be grateful that you didn’t fight to the death with Ayesha over inlining objects in props.

当然，有时候您需要重视代码和性能。 到那时，您将不因未将Ayesha插入道具中而与Ayesha战斗而感激不已。

使用功能强大的编辑器，并重视Intellisense和打字。 (Use a powerful editor, and value Intellisense and Typings.)

How often do you find yourself having to switch files just to figure out what order a function’s arguments are in? What about if it takes a string or a number for the size argument?

您多久发现自己不得不切换文件才能弄清楚函数参数的顺序？ 如果size参数使用字符串或数字怎么办？

Being knocked out of your workflow leads to mental fatigue. Having to look up documentation to see what functions are available to you stinks. I personally use VSCode and TypeScript, but use whatever works best for you.

被淘汰出工作流程会导致精神疲劳。 必须查阅文档才能发现您可以使用哪些功能。 我个人使用VSCode和TypeScript，但使用最适合您的方法。

花一些时间向周围的人传播正能量 (Spend some time spreading positive energy to those around you)

Have you ever wished that while you are sitting there struggling that someone would come up to you, and just ask you how you are doing? Maybe just to grab a bite to eat?

您是否曾经想过，当您坐在那里苦苦挣扎时有人会来找您，问您最近怎么样？ 也许只是想吃点东西？

You can’t control if others do that for you, but you can control if you do that for others. Not only will it make someone’s day, but I guarantee they won’t forget your kindness.

您无法控制其他人是否为您这样做，但是您可以控制是否为他人这样做。 这不仅会成为某人的一天，而且我保证他们不会忘记您的好意。

Influencing good culture is just as valuable to me as good code. Empathy and kindness scale, douchebaggery does not.

对我而言，影响良好的文化与良好的代码一样有价值。 同理心和善良的尺度，douchebaggery没有。

If you have any questions or are looking for one-on-one React mentorship, feel free to tweet me @yurkaninryan any time!

如果您有任何疑问或正在寻找一对一的React指导，请随时在@yurkaninryan上发消息给我！

If you like my writing style, here are some other articles that I’ve done.

如果您喜欢我的写作风格，这是我做过的其他文章。

Good luck and happy coding! ??

祝您好运，编码愉快！ ??

翻译自: https://www.freecodecamp.org/news/how-to-get-back-on-track-after-youve-burned-out-programming-a04ccafeefd6/

游泳后精疲力尽