影像锐化工具

by Harshdeep S Jawanda

通过Harshdeep S Jawanda

如何以及为什么要进行工具改造：花在锐化斧头上的时间永远不会浪费 (How and why you should tool-up: time spent sharpening your axe is never wasted)

There is this old anecdote about two friends who went to the forest to chop up some firewood for their homes. The first friend kept at it without a break for four hours, whereas the other friend would rest for 5 minutes or so every hour. When they were done the first friend was surprised to see that the other’s woodpile was much larger than his.

这个古老的故事讲述了两个朋友去森林砍柴为家。 第一个朋友在这里休息了四个小时，而另一个朋友每小时要休息5分钟左右。 当他们做完后，第一个朋友惊讶地发现对方的木头堆比他的大得多。

Incredulous, he asked, “How did you chop more wood than me!? I worked continuously while you took so many breaks.”

他怀疑地问道：“你怎么砍了比我还多的木头！？ 您休息了这么长时间，我一直在工作。”

His friend replied, “While resting, I would sharpen my axe, so that I could chop up wood more efficiently the rest of the time.”

他的朋友回答说：“在休息的同时，我会锐化斧头，以便在剩下的时间里更有效地砍柴。”

That’s what I mean by “Tool-Up!”: equipping yourself with the right tools to make you more productive while ensuring higher quality work output.

这就是我所说的“动手做！”的意思：为自己配备合适的工具，以提高工作效率，同时确保更高质量的工作输出。

What follows is aimed at developers, and uses Java to illustrate examples. But the general advice applies to everybody.

接下来的内容面向开发人员，并使用Java举例说明。 但是一般性建议适用于每个人 。

放聪明点 (Be smart)

The example above is not to meant to send you running to your keyboard to start banging out utility classes/libraries that will supposedly help you out. Not at all! Be smart about what exactly it is that you need. Maximize the Return On your (time) Investment (ROI). An important part of being smart means that you…

上面的示例并不是要让您奔跑到键盘上来开始敲响应该可以帮助您的实用程序类/库。 一点也不！ 明智地了解您到底需要什么。 最大化您(时间)的投资回报率(ROI)。 聪明的重要一环意味着您……

更喜欢预先构建的解决方案来推出自己的解决方案 (Prefer pre-built solutions to rolling out your own)

For developers, the right tool is often a library that provides you with the required functionality. Whether it is the Optional<;T> class of the Guava library (for use in pre-Java 8 code) or its ImmutableList<T> implementation, these tools have been developed to cover many use cases. They also typically have many generations of evolution behind them, and have been thoroughly tested, both by developers and by users. As such they offer the benefits of good design and mature implementations.

对于开发人员而言，正确的工具通常是为您提供所需功能的库。 无论是Guava库的Optional< ; T>类(供Java 8之前的代码使用)还是r its ImmutableL <T>实现，这些工具都已开发为涵盖许多用例。 它们通常还具有许多代的演变过程，并且已经过开发人员和用户的全面测试。 因此，它们提供了良好的设计和成熟的实现的好处。

Remember: don’t re-invent the wheel!

记住：不要重新发明轮子！

始终使用您的工具 (Use your tools consistently)

If you use a tool or technique, try to use it consistently throughout your work as much as you’re able. This will help reduce the mental load of having to do a context switch between different paradigms and situations.

如果您使用工具或技术，请​​尝试在整个工作中尽可能地一致地使用它。 这将有助于减轻必须在不同的范式和情况之间进行上下文切换的精神负担。

Often this means refactoring legacy code. In such situations, you should seriously consider scheduling time for it. If time is a limiting factor — as it often is — try to prioritize high-impact parts of your codebase.

通常，这意味着重构遗留代码。 在这种情况下，您应该认真考虑安排时间。 如果时间(通常是时间)是一个限制因素，请尝试确定代码库中影响较大的部分的优先级。

何时该自己做 (When it’s time to do it yourself)

The stage will likely come (as it almost invariably does) that pre-built solutions are not good enough, or they fail to fill some of the very specific gaps you need filled. Don’t feel pressured to create humongous, perfectly-designed, everything-and-the-kitchen-sink libraries. Start small. Create a solution that’s just enough for your current needs. Perhaps instead of creating a library, think only about creating a utility class, and then take things from there.

预先建立的解决方案可能还不够好，或者无法填补您需要填补的某些非常具体的空白(几乎总是如此)。 创建巨大的，设计完美的，万事俱备的厨房接收器库时不要感到压力。 从小开始 。 创建一个足以满足您当前需求的解决方案 。 也许不用创建一个库，而只考虑创建一个实用程序类，然后从那里开始。

一点可以走很长的路 (A little can go a long way)

You’ll be surprised by how much utility and convenience even 3–4 lines of ordinary code can deliver.

您甚至会对3至4行普通代码所能提供的实用性和便利性感到惊讶。

There were a number of places in my code where I had to get specific values from specific indices in Lists. What’s more simple than:

我的代码中有很多地方必须从List的特定索引中获取特定值。 比这更简单：

Object listValue = myList.get(index)

Right? Not so fast! That simple line of code can potentially throw two different exceptions (can you figure out which ones and why?). Ok, so you wrap your code with some try-catch goodness and now you’re done, right? What value are you going to assign to listValue in case of an exception? Your code now begins to look something like:

对？ 没那么快！ 这段简单的代码可能会引发两个不同的异常(您能找出哪个异常以及为什么吗？)。 好的，因此您将代码包装为具有try-catch优点，现在就完成了，对吗？ 如果发生异常，您要为listValue分配什么值？ 您的代码现在开始看起来像：

Object listValue = null; // default value assignmenttry {    listValue = myList.get(index);} catch (Exception e) {    // Do nothing (if that is what you want to do)}

Simple, straightforward code — but it’s not exactly a pretty sight or very convenient. Not to mention that similar fragments will be littered all over your code. Sooner or later you will also forget to cater for all eventualities. And then: boom!!

简单，直接的代码-但这并不完全是视觉效果或非常方便。 更不用说类似的片段会在您的代码中乱七八糟。 迟早您还会忘记照顾所有可能发生的情况。 然后： 繁荣！

Compare that to:

比较一下：

Object listValue = Lists.get(myList, index, null);

where the Lists utility class contains the following convenience method:

Lists实用程序类包含以下便捷方法：

public static <T> T get(List<T> list, int position, T defaultValue) {    if (null != list && position >= 0 && position < list.size())        return list.get(position);    return defaultValue;}

It’s an extremely simple method, yet very useful (for a specific use case).

这是一种非常简单的方法，但非常有用(对于特定的用例)。

Of course, this may not be exactly what you need. You could also argue that instead of throwing an ArrayIndexOutOfBounds exception, this code hides incorrect indices and could lead to insidious errors, and that’s why you don’t find code like this in general-purpose libraries (where failing early is a virtue)…That’s all valid, but that is also why I wrote this particular utility method for my use case.

当然，这可能并不是您真正需要的。 您还可能会争辩说，此代码没有引发ArrayIndexOutOfBounds异常，而是隐藏了错误的索引并可能导致隐患，这就是为什么您在通用库中找不到这样的代码(尽早失败是一种美德)的原因……全部有效，但这也是为什么我为用例编写了这种特殊的实用程序方法的原因。

This illustrates my point: beyond the point you can/will/should write utility code for your specific use cases, just be aware of potential pitfalls, if any.

这说明了我的观点：超出您可以/将/应该为您的特定用例编写实用程序代码的时候，请注意潜在的陷阱(如果有)。

寻找重复的图案 (Look for repeating patterns)

As I mentioned before, there’s no need to rush into anything. A good and easy way to identify scenarios where a higher level of abstraction would be useful is to look for things that are:

正如我之前提到的，无需着急。 确定较高抽象级别的方案的简便方法是查找以下内容：

• cumbersome
  麻烦的
• have repeated usage
  反复使用
• are error-prone
  容易出错

Let this be your guide. Basically, look for repeating patterns in your code or your actions to get the most bang for your buck.

让这作为您的指南。 基本上，在代码或操作中寻找重复的模式 ，以最大程度地发挥作用。

As you start to improve the most obvious scenarios, other — often higher-level — patterns will begin to emerge. Things that did not seem so inconvenient before will suddenly start looking unweildy/error-prone in comparison. That will automatically guide you towards the next tool/abstraction you should develop.

随着您开始改善最明显的场景，其他(通常是更高级别)的模式将开始出现。 与以前相比，以前似乎不太方便的事情将突然看起来不可靠/容易出错。 这将自动指导您进行下一个应开发的工具/摘要。

Rinse, repeat.

冲洗，重复。

不要强迫 (Don’t Force It)

Let your tool usage/adoption grow organically as you deal with your pain points and bottlenecks (Agile mindset?). Don’t set a hard-coded limit of X hours spent per week to satisfy some externally-imposed metric of what constitutes “good practice.”

当您处理痛点和瓶颈时(敏捷思维方式？)，让您的工具使用/采用方式有机地增长。 不要设置每周花费X个小时的硬编码限制，以满足构成“良好实践”的某些外部指标。

Forced tool usage can sometimes be counter-productive: you’ll get much better results when you and your people feel the need for improvement. The motivation level and the perception of reward (when the improvement happens) is just so much higher.

强迫使用工具有时会适得其反：当您和您的员工感到需要改进时，您将获得更好的结果。 动机水平和对奖励的感知(当改进发生时)要高得多。

最后但并非最不重要的…… (Last but definitely not least…)

Practice continuous learning and self-improvement.

练习不断学习和自我完善。

These are the two most important tools you can equip yourself with. Once you inculcate these habits, they will have the longest-lasting impact on your life and career.

这是您可以装备的两个最重要的工具。 一旦您养成这些习惯，它们就会对您的生活和职业产生最长久的影响。

最后… (Finally…)

If you found this article helpful, please don’t forget to clap ;-)!

如果您发现这篇文章对您有所帮助，请别忘了鼓掌;-)！

Constructive discussions and corrections are most welcome.

欢迎进行建设性的讨论和更正。

翻译自: https://www.freecodecamp.org/news/how-and-why-you-should-tool-up-time-spent-sharpening-your-axe-is-never-wasted-ef74e05e85d0/

影像锐化工具