A green field project unfolds in front of you. Fresh software technologies, ripe for the picking, await discovery. You’re excited, engaged, and ready to embark on a new journey.

一个绿色的项目在您面前展现。 可供选择的成熟软件新技术正在等待发现。 您会兴奋，投入并准备开始新的旅程。

Then you pause.

然后你停下来。

How do you choose technologies to review? How do you start to learn them? How do you become sufficiently expert to make a choice?

您如何选择要审查的技术？ 您如何开始学习它们？ 您如何成为足够的专家来做出选择？

第1步-研究您的选择 (Step 1 — Research Your Options)

With so many technologies available, you need to narrow the beam down to a short list. Don’t make the mistake of just picking the latest and greatest. Technologies come and go and what is trending today, maybe tomorrow’s also ran.

有了这么多可用的技术，您需要将波束范围缩小到一个简短的列表。 不要仅仅选择最新的和最大的错误。 技术来了又去了，今天的趋势，也许明天的趋势也在运行。

How do you choose in such a crowded marketplace? A few key questions I ask are:

在如此拥挤的市场中，您如何选择？ 我要问的几个关键问题是：

1. Is it open source with a permissive license? Modern open source stacks are excellent and there is little reason to risk vendor lock-in.

   它是带有许可许可证的开源软件吗？ 现代开源堆栈非常好，几乎没有理由冒供应商锁定的风险。

2. Is it established, mature and under active development? If I’m looking at an application which can be maintained beyond the length of the project, this is very important. If it may be me or my team returning to it in the future, even more so.

   它是否已经建立，成熟并且正在积极发展？ 如果我正在寻找可以在项目范围之外进行维护的应用程序，那么这非常重要。 如果是我本人或我的团队将来再来，那就更是如此。

3. Does it do everything you need? There is little point in using a new technology which won’t help you to deliver your application. Moreover, if the technology does far more than you need, the learning curve and ongoing maintenance may be undesirable. Bare in mind, a hotchpotch of differing technologies strapped together, may also lead to trouble; think ahead, consider the medium to long term requirements, rather than just what you need now.

   它能满足您的所有需求吗？ 使用不会帮助您交付应用程序的新技术毫无意义。 此外，如果这项技术的功能远远超出您的需求，那么学习曲线和持续的维护可能就是不希望的。 切记，捆绑在一起的各种技术的热点也可能导致麻烦。 提前考虑，考虑中长期需求，而不只是现在的需求。

4. Is there good documentation? If the developers of the technology are unable to easily explain how it works, what hope do you have as an outsider? Good, foundational, documentation, and simple tutorials are worth their weight in gold.

   有好的文件吗？ 如果该技术的开发人员无法轻松解释其工作原理，那么作为局外人您有什么希望？ 好的，基础的，文档的和简单的教程值得一试。

5. Is there an active community? As any developer knows, search engines are your friend. Stack Overflow is littered with fallen comrades seeking help, with others lifting them back to their feet. It is easier to learn from those who fell before you, than being the person who falls.

   有活跃的社区吗？ 任何开发人员都知道，搜索引擎是您的朋友。 堆栈溢出堆满了堕落的同志，他们寻求帮助，其他人则将他们抬起脚来。 向跌倒的人学习比倒下的人容易。

6. Is there a pool of experienced developers available? If the application becomes a success, the team will need to grow to maintain it and support new features. If you pick an esoteric solution, this could lead to an unmanageable application in the future. Some applications may even need to be rewritten to keep them moving forward.

   有大量经验丰富的开发人员吗？ 如果该应用程序成功，则团队将需要扩展以维护它并支持新功能。 如果您选择一个深奥的解决方案，这可能会导致将来无法管理的应用程序。 某些应用程序甚至可能需要重写以使它们继续前进。

7. Is the technology opinionated or highly customizable? I’ll be controversial and say I only have time for opinionated technologies, unless there is a very good reason to go with flexibility. I’m experienced (old?) enough to have seen many applications become a mess of yesterday’s technologies and it just isn’t worth it. Unless there are killer features that are needed, trust those who came before you — their opinions were likely based on experience.

   技术是自以为是还是高度可定制的？ 我会有争议，说我只有时间自以为是的技术，除非有很好的理由去与灵活性。 我有足够的经验(已经过时了？)，以至于看到许多应用程序变成了昨天的技术的烂摊子，但这并不值得。 除非需要一些杀手级功能，否则请相信那些在您之前出现的人-他们的观点很可能是基于经验的。

8. Does the technology fit around the core application technologies? Depending on just how ‘green field’ the application is, this may apply to a lesser or greater degree. For example, you may decide that Java and TypeScript are a necessity, which will rule out many other options.

   该技术是否适合核心应用技术？ 根据应用程序的“绿色领域”的程度，它可能会或多或少地适用。 例如，您可能认为Java和TypeScript是必需的，这将排除许多其他选项。

9. What do your fellow developers think? You may know others in your network who are specialists in the field. They may have very strong opinions on what is good, bad or ugly. It is often flattering to be asked for your opinion — it is nice to know it is valued — and you may learn something key.

   您的其他开发人员怎么看？ 您可能认识到您网络中的其他专家。 他们对什么是好，坏或丑陋可能有很强烈的意见。 征求您的意见通常很讨人喜欢-很高兴知道它的价值-您可能会学到一些关键的知识。

This checklist should narrow the options down to a small handful, your shortlist. Maybe even one, if you are lucky.

此清单应将选择范围缩小到少数几个您的候选清单。 如果幸运的话，甚至一个。

第2步-完成教程申请 (Step 2 — Complete a Tutorial Application)

Nothing gives you a better taste for a new technology than following a basic tutorial. You gain insight into how easy it is to get something basic off the ground.

跟随基础教程，没有什么比给您更好的新技术体验了。 您将获得深入了解基础知识的难易程度。

I’d recommend configuring your favourite IDE (or your new IDE!) to see how well your tooling fits. There may be native support, which will help you to complete the tutorial. This could be anything from a language template (colour coding, indenting, etc.) to helpers to create modules, add boiler plate and so forth.

我建议配置您喜欢的IDE(或新的IDE！)，以查看工具的适用性。 可能会有本机支持，这将帮助您完成本教程。 从语言模板(颜色编码，缩进等)到帮助程序来创建模块，添加样板等等，这些都可以。

Once you have completed the tutorial, you should have an idea of how well things fit together. Did it feel familiar? Did it feel overly complex? Did it feel too rigid or too relaxed? Write some notes about the technology, capturing the salient points.

学习完本教程后，您应该对各方面的融合情况有所了解。 觉得熟悉吗？ 感觉太复杂了吗？ 感觉太僵硬还是太放松？ 写一些有关该技术的注释，以抓住要点。

步骤3 —自定义教程应用程序 (Step 3 — Customise the Tutorial Application)

A good way to test your understanding and the capabilities of the technology, is to make it do something more complicated. Using the foundation built in the tutorial, you can quickly tack on new functionality.

检验您的理解和技术功能的一种好方法是使它做的事情更复杂。 使用教程中内置的基础，您可以快速使用新功能。

The new functionality can be anything you like. Make sure it is complex enough to push past the perimeters of the tutorial. It needs to be meaty enough that a solution is not obvious, but I wouldn’t spend more than a few days on it. Your creation doesn’t need to be super refined either, as you are just proving the concept.

新功能可以是您喜欢的任何东西。 确保它足够复杂以超出本教程的范围。 它需要足够多的肉，以至于解决方案并不明显，但是我不会花几天以上的时间。 您的创作也不需要超精炼，因为您只是在证明这一概念。

This is where the technology’s documentation and community will face its first test. You will be straying off the beaten tutorial track.

这是该技术的文档和社区将面临的首次测试的地方。 您将流连忘返。

I usually start by reading the first few chapters of the documentation. This will give me an understanding into the background of the technology and an overview on how it is glued together. From this, I can start referencing key points, either through other specific chapters or search engines.

我通常从阅读文档的前几章开始。 这将使我对技术的背景有一个了解，并概述了如何将其粘合在一起。 由此，我可以通过其他特定章节或搜索引擎开始引用关键点。

Depending on how much experience you have, this process may be long or short. You may quickly see parallels with technologies you are already familiar with. The architecture may be similar and well trodden design patterns may be present. This will give you immediate comfort, allowing you to make useful assumptions about how it ticks.

根据您的经验，这个过程可能长短不一。 您可能会很快看到与您已经熟悉的技术的相似之处。 该体系结构可能是相似的，并且可能会出现很多常见的设计模式。 这将给您立即的舒适感，使您可以对它如何滴答做出有用的假设。

If everything feels alien, all is not lost — it may just be something new to crack. If you are relatively experienced and it still feels awkward, perhaps it is time to consider another technology on your shortlist? You can always come back again.

如果一切都变得陌生，那么一切都不会丢失–可能只是一些新东西需要破解。 如果您比较有经验，但仍然感到尴尬，也许是时候考虑入围另一项技术了？ 您随时可以再次回来。

Was it easy to add your custom functionality? Did you get stuck often? Was it easy to get unstuck after reading the documentation? Did you fall back on the community? Was it evident that people had solved similar issues or was it tough to find answers? Take notes on these points too.

添加自定义功能容易吗？ 你经常被困吗？ 阅读文档后容易被卡住吗？ 您是否回到了社区？ 是否已经证明人们已经解决了类似的问题，还是很难找到答案？ 也要注意这些方面。

步骤4 —部署应用程序 (Step 4 — Deploy the Application)

While an application may be a walk in the park to write, some can be a pain to deploy. What better way to find out than by doing a test deployment?

虽然应用程序可能是编写过程中的麻烦事，但某些应用程序可能很难部署。 有什么比进行测试部署更好的发现方法？

I start by looking at how easy it is to package and containerise. If there is a back end component, is it easy to put it in a Docker container? This will immediately open up a world of cloud options. Once containerised, I know that I can slot it into a CI/CD pipeline easily too.

我首先看包装和集装箱化有多容易。 如果有后端组件，是否容易将其放在Docker容器中？ 这将立即打开云选项的世界。 容器化后，我知道我也可以轻松地将其插入CI / CD管道。

If the deployment process is arduous, can’t be scripted nor containerised, I will likely move onto a different technology. I prefer to spend more time writing applications, rather than installing and deploying them.

如果部署过程很繁琐，既不能编写脚本也不能进行容器化，那么我可能会转向另一种技术。 我宁愿花更多的时间来编写应用程序，而不是安装和部署它们。

步骤5 —查看您的技术候选清单 (Step 5 — Review Your Technology Shortlist)

By this point, you should have at least completed the tutorial and tried to extend it in some way. You should have lots of notes too. You have probably already picked a winner and are looking forward to getting stuck into application development.

至此，您至少应该已经完成​​了本教程并尝试以某种方式进行扩展。 您也应该有很多笔记。 您可能已经选择了一个赢家，并期待着参与应用程序开发。

What if it is too close to call? Take another look at the original list in step 1. Are there any differences here that could split the pack? Perhaps your network of contacts can help you decide?

如果距离太近怎么办？ 再看一下第1步中的原始列表。这里是否有其他差异可以拆分包？ 也许您的联系人网络可以帮助您做出决定？

Once you have reviewed the options, you could opt to convert your notes into a formal review document. Your company may have internal processes for evaluating new technologies. Perhaps your direct client wishes to understand your decision instead. Showing your working will give them confidence that you have been duly diligent.

审核完选项后，您可以选择将笔记转换为正式的审核文档。 您的公司可能具有评估新技术的内部流程。 也许您的直接客户希望了解您的决定。 展示您的工作将使他们充满信心，相信您一直在勤奋工作。

摘要 (Summary)

You will need to recommend, choose or use new technologies frequently in your software development career. I recently found myself doing this again and thought my approach may be worth sharing. Thanks for reading!

在您的软件开发生涯中，您将需要经常推荐，选择或使用新技术。 我最近发现自己再次这样做，并认为我的方法可能值得分享。 谢谢阅读！