如何利用 "为什么、什么、如何 "框架更好地写作

Here’s a story from the early days of Amazon Web Services: Before writing any code, engineers spent 18 months contemplating and writing documents on how best to serve the customer. Amazon believes this is the fastest way to work—thinking deeply about what the customer needs before executing on that rigorously refined vision.

这里有一个来自亚马逊网络服务早期的故事。在编写任何代码之前,工程师们花了18个月的时间来思考和编写关于如何最好地服务客户的文件。亚马逊认为这是最快的工作方式--在执行严格完善的愿景之前,深入思考客户的需求。

Similarly, as a data scientist, though I solve problems via code, a lot of the work happens before writing any code. Such work takes the form of thinking and/via writing documents. This is especially so in Amazon, which is famous for its writing culture.

同样,作为一个数据科学家,虽然我通过代码解决问题,但很多工作都是写代码之前发生的。这种工作的形式是思考和/或通过写文件。在以写作文化而闻名的亚马逊,情况更是如此。

This post (and the next) answers the most voted-for question on the topic poll:

这篇文章(和下一篇)回答了主题投票中投票最多的问题。

How to write design documents for data science/machine learning projects?

如何编写数据科学/机器学习项目的设计文档?

I’ll start by sharing three documents I’ve written: one-pagers, design documents, and after action reviews. Then, I’ll reveal the framework I use to structure most of my writing, including this post. In the next post, we’ll discuss design docs.

我将首先分享我写的三个文件:单页纸、设计文件和行动后的回顾。然后,我将揭示我用来组织我大部分写作的框架,包括这篇文章。在下一篇文章中,我们将讨论设计文件。

One-pagers, design docs, after-action reviews

单页文件、设计文件、行动后审查

I usually write three types of documents when building/operating a system. The first two help to get alignment and feedback; the last is used to reflect—all three assist with thinking deeply and improving outcomes.

在建立/运作一个系统时,我通常写三种类型的文件。前两种有助于获得一致性和反馈;最后一种用于反思--所有这三种都有助于深入思考和改善结果。

The three types of documents written during a project

The three types of documents written during a project

项目期间撰写的三种类型的文件

One-pagers: I use these to achieve alignment with business/product stakeholders. Also used as background memos for quarterly/yearly prioritization. In a single page, they should allow readers to quickly understand the problem, expected outcomes, proposed solution, and high-level approach. Extremely useful to reference when you’re deep in ...

开通本站会员,查看完整译文。

Accueil - Wiki
Copyright © 2011-2024 iteam. Current version is 2.137.1. UTC+08:00, 2024-11-15 10:23
浙ICP备14020137号-1 $Carte des visiteurs$