返回新列表，且排好序了，升序，原 listxx不变 ②set数据操作（无序，数值不重复） ★若在创建set时，有多个重复的元素，则只会存储其一，元素只能是 不可变对象 t=("wh","fdjs","fkdsl") setyy=frozenset(t) # 创建不可变set，无add remove update操作 setxx.add("xxx") # 新增元素 timestr="Tue Apr 05 22:22:15 2022" t=time.strptime(timestr,"%a %b %d %H:%M:%S %Y") print(t) print(type(t)) ⑤时间结构体转为时间戳 import time timestr="Tue Apr 05 22:22:15 2022" t=time.strptime(timestr,"%a %b %d %H:%M:%S %H:%M:%S %Y") tstamp=time.mktime(t) #时间结构体转为时间戳 print(tstamp) #结果 1649168535.0 ⑥暂停线程的运行 import time time.sleep(5) #单位为 秒 ★os操作系统接口模块

the Church of Graphs. If it moves, we track it. Sometimes we’ll draw a graph of something that isn’t moving yet, just in case it decides to make a run for it…Tracking everything is key to moving fast INFRASTRUCTURE i. Remove the silos of information – Developers don’t just log what’s interesting to development. Operations don’t just monitor what’s up or down. ii. Modern Monitoring architecture breaker trips 11. Delays 12. Backup success/failure d. USE TELEMETRY TO GUIDE PROBLEM-SOLVING i. Don’t practice “Mean Time until Declared Innocent” – culture of blame encourages limited documentation, hiding

predictability, control, and efficiency, the key values of the contractor-control model. But it doesn’t. Requirements: Requirements are a way of controlling the development team by constraining their creativity something that is a near fit, and then deal with the question of whether it is a near enough fit.I don’t mean that standards are bad. Let’s just agree that they might be overrated. A Better Way – Treat IT individual products, it is lumpy rather than smooth. The products don’t quite fit together; they have excess capabilities that we don’t really need; the ball has strange gaps where it is unexpectedly hollow

million mandatory fields and most of the time, the drop down boxes for ‘applications affected’ don’t even have what I need. It’s why I’ve stopped even putting in change requests.”  “I have to manually done. We can’t wait for you to hem and haw, complaining that we didn’t fill out the form right.” Lesson: Don’t let your change control process become a change prevention process. Don’t let your change

Everything Is Relative – Even When It Shouldn’t Be  Examples: House Shopping, Vacations,  Observations: o “humans rarely choose things in absolute terms. We don’t have an internal value meter that tells bonuses vs. recognition and appreciation The Problem of Procrastination and Self-Control – Why We Can’t Make Ourselves Do What We Want to Do  Example: Vehicle Maintenance, E-mail  Experiment: Class paper perhaps more than we should. And most frequently, we have trouble letting go of it because we can’t stand the idea of its loss. What are we left with then? An ideology- rigid and unyielding”  Agile

specific metrics observed, investigative paths taken, results, and other resolutions considered 2. Don’t allow fear of punishment or retribution creep in due to words or behaviors – find a facilitator to Netflix – a single engineer had been responsible for taking down Netflix twice in 18 month span. He wasn’t fired, he had also helped move their operations and automation forward by “light-years” and had performed versus private knowledge from emails b. AUTOMATE STANDARDIZED PROCESSES IN SOFTWARE FOR RE-USE i. Don’t store standards and processes in Word or non-actionable documents; leads to fragmentation, fragility

risks in our daily work 2. we learn from our successes and failures, identifying which ideas don’t work and reinforcing those that do3. local learnings are rapidly turned into global improvements, so DAILY WORK 1. Mike Rother observed in Toyota Kata that in the absence of improvements, processes don’t stay the same—due to chaos and entropy, processes actually degrade over time. 2. We improve daily weeks f. RESERVE 20% OF CYCLES FOR NON-FUNCTIONAL REQUIREMENTS AND REDUCING TECHNICAL DEBT i. Don’t just make the interest payments, pay down the principle ii. If not managed, services become so fragile

GitCommit:"89a4ea3e1e4ddd7f7572286090359983e0387b2f", GitTreeState:"clean", BuildDate:"2023-09-13T09:34:32Z", GoVersion:"go1.20.8", Compiler:"gc", Pla�orm:"linux/amd64"} # kubeadm config images �gera-operator NAME READY STATUS RESTARTS AGE �gera-operator-59b69c49dc-t6crt 1/1 Running 1 (10m ago) 51m # kubectl get pods -n calico-system NAME calico-node-qn7cp 1/1 Running 1 (10m ago) 11m calico-typha-84cb54bfd-hh57t 1/1 Running 1 (10m ago) 11m csi-node-driver-fn7zd

representing the first time we see how an application behaves in a production-like environment ii. Don’t just document the environment specifications 1. Create a common build mechanism to create it on demand tests – test application as a whole that functionality operates as designed and regressions haven’t been introduced iv. Integration tests – ensure correct interaction with other production applications different test categories to run in parallel iii. Generally, limit manual testing if automated tests haven’t passed iv. For resource intensive suites, performance tests, IA, execute as frequently as possible

Code quality - can't scale crappy code  Program execution  Alignment  Transparency House of Lean: "We need to figure out a way to deliver software so fast that our customers don't have time to change