tools rather than static 3. Graph business metrics with infrastructure metrics to provide deeper context iv. Overlaying other relevant information onto our metrics 1. All production deployments should with website conversion rates up 50% b. A BRIEF HISTORY OF A/B TESTING i. Pioneered in direct response marketing ii. Early efforts required sending thousands of postcards/flyers and asking consumer or those relevant to production incidents 1. Bad pull requests – typically doesn’t have enough context for the reader, little documentation of the changes intended outcome, or explanation of the thought

#使用 import requests response = requests.get("http://sysyear.top:4600") print(type(response.text)) # 类型为str response.encoding = "utf-8" # 指定返回数据的文本编码 print(response.status_code) # 返回http响应状态码 返回http响应状态码 print(response.headers) # 返回http头部信息，单行字典类型 print(response.text) # 返回正文内容，多行文本 import requests myurl = "http://sysyear.top:4600" myheaders = { "Accept": "application/json" "Content-Type": "application/json;charset=utf8" } mydata = "dddd" response = requests.post(myurl, headers=myheaders, data=mydata, verify=False) response.encoding = "utf-8" # 指定返回数据的文本编码 ★selenium（浏览器url操作）

ernetes/pki/kube-user01.key #创建context上下文 # kubectl config set-context kube-user01@kubernetes --cluster=kubernetes -- user=kube-user01 # kubectl config use-context kube-user01@kubernetes #切换上下文（指定使用 #切换上下文（指定使用 kube-user01用户去访问k8s集群，此用户目前没有访问集群的权限 # kubectl config use-context kubernetes-admin@kubernetes #切换回管理员用 户 # kubectl --context=kube-user01@kubernetes get pods #临时使用某用户上下 文 ②创建服务账号ServiceAccount apply -f rolebinding-pods-reader.yaml 然后kube-user01用户就有了读取default名称空间中的pods资源的权限 # kubectl --context=kube-user01@kubernetes get pods #此用户有了获取 pods的权限 ★同一用户可以通过多个rolebinding绑定多个role

center in queues and making it visible, all stakeholders can more easily prioritize work in the context of global goals. ii. REDUCE BATCH SIZES1. Another key component to creating smooth and fast flow update other services. iii. Decouple from shared infrastructure – shared databases iv. Bounded context – compartmentalized and well-defined interfaces k. KEEP TEAM SIZES SMALL (THE “2-PIZZA TEAM” RULE)

understand team goals in the context of organization goals, provide feedback and guidance as early as possible ii. Awareness and involvement provides better business context for risk-based decisions

vision, that they understand the business’s intent, and that they will make decisions within the context of that intent.  How will the team determine the specific requirements—that is, determine what