Engineering work is novel and intrinsically requires human judgment. It produces a permanent improvement in your service, and is guided by a strategy. It is frequently creative and innovative, taking a design-driven approach to solving a problem—the more generalized, the better. Engineering work helps your team or the SRE organization handle a larger service, or more services, with the same level of staffing.
工程工作是新颖的，本质上需要人的判断。它在你的服务中产生永久性的改进，并以一种战略为指导。它经常是创造性和革新性的，采取一种设计驱动的方法来解决一个问题--越普遍越好。工程工作帮助你的团队或SRE组织在相同的人员配置水平下处理更大的服务，或更多的服务。
Typical SRE activities fall into the following approximate categories:
- Software engineering. Involves writing or modifying code, in addition to any associated design and documentation work. Examples include writing automation scripts, creating tools or frameworks, adding service features for scalability and reliability, or modifying infrastructure code to make it more robust.
- Systems engineering. Involves configuring production systems, modifying configurations, or documenting systems in a way that produces lasting improvements from a one-time effort. Examples include monitoring setup and updates, load balancing configuration, server configuration, tuning of OS parameters, and load balancer setup. Systems engineering also includes consulting on architecture, design, and productionization for developer teams.
- Toil. Work directly tied to running a service that is repetitive, manual, etc.
- Overhead. Administrative work not tied directly to running a service. Examples include hiring, HR paperwork, team/company meetings, bug queue hygiene, snippets, peer reviews and self-assessments, and training courses.
典型的SRE活动大致分为以下几类：
- 软件工程。除了任何相关的设计和文档工作外，还涉及到编写或修改代码。例如，编写自动化脚本，创建工具或框架，为可扩展性和可靠性增加服务功能，或修改基础设施代码以使其更加强大。
- 系统工程。涉及配置生产系统，修改配置，或记录系统的方式，通过一次性的努力产生持久的改善。例如，监控设置和更新，负载均衡配置，服务器配置，操作系统参数的调整，以及负载均衡器的设置。系统工程还包括为开发者团队提供架构、设计和生产方面的咨询。
- 劳作。与经营一项服务直接相关的工作，是重复性的，手工的，等等。
- 间接费用。与运行服务没有直接联系的行政工作。例如，招聘、人力资源文书工作、团队/公司会议、错误队列清理、片段、同行评审和自我评估以及培训课程。
Every SRE needs to spend at least 50% of their time on engineering work, when averaged over a few quarters or a year. Toil tends to be spiky, so a steady 50% of time spent on engineering may not be realistic for some SRE teams, and they may dip below that target in some quarters. But if the fraction of time spent on projects averages significantly below 50% over the long haul, the affected team needs to step back and figure out what’s wrong.
每个SRE都需要花至少50%的时间在工程工作上。劳作往往是尖锐的，所以对一些SRE团队来说，稳定地将50%的时间花在工程上可能不现实，他们可能在某些季度低于这个目标。但是，如果长期以来，花在项目上的时间比例明显低于50%，受影响的团队就需要退一步，找出问题所在。
Back to contents of the chapter（返回章节目录）
- Previous Section（上一节）：Why Less Toil Is Better（为什么更少的劳作更好）
- Next Section（下一节）：Is Toil Always Bad?（劳作总是不好的吗？）