Create a common build mechanism to create it on demand 2. Codified in automated environment build process iii. Environments will be stable, reliable, consistent, & secure c. CREATE OUR SINGLE REPOSITORY production instances v. Keep developers’ environments most current e. MODIFY OUR DEFINITION OF DEVELOPMENT “DONE” TO INCLUDE RUNNNING IN PRODUCTION-LIKE ENVIRONMENTS i. In general, the longer the interval frequently as possible i. WRITE OUR AUTOMATED TESTS BEFORE WE WRITE THE CODE (“TEST DRIVEN DEVELOPMENT”) i. TDD – Kent Beck as part of Extreme Programming 1. Ensure the tests fail – “Write a test

contractor-control model. But it doesn’t. Requirements: Requirements are a way of controlling the development team by constraining their creativity. Instead of requirements, we want to charge the team—the by:  limiting agility and adding bureaucratic waste: exceptions must be put through an approval process  standardization limits the space of possible solutions to a problem.  if we mandate that projects changes to the whole ball of EA.  It has a robust, automated regression test suite, so that new development does not cause expensive break-fix activity.  It has good monitoring tools in place.  It is

understand contributing factors and focus problem-solving. ii. Telemetry – An automated communications process by which measurements and other data are collected at remote points and are subsequently transmitted 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 1. Data iii. More exotic - Fast Fourier Transforms or Kolmogorov-Smirnov 4. Ch. 16 – Enable Feedback So Development and Operation Can Safely Deploy Code a. USE TELEMETRY TO MAKE DEPLOYMENTS SAFER i. Actively monitor

stick to a plan. Lean thinking gives that small team ways to speed up its inspecting and adapting process to maximize its impact. Continuous Delivery and DevOps place the entire value stream in the hands entire value delivery process. Brining Lean Principles to Software Development: Kanban is David Anderson’s approach to bringing Lean principles into software development while driving fear fear out of the transformation process through incremental change. Anderson provides four rules for implementing Kanban: 1. Start with existing processes 2. Pursue incremental, evolutionary change 3.

a way that focuses on the situational aspects of a failure’s mechanism and the decision- making process of individuals proximate to the failure.” – John Allspaw ii. Blameless Post-Mortem – Actions: 1 NFRs. Codify these into the tests and pipeline f. BUILD REUSABLE OPERATIONS USER STORIES INTO DEVELOPMENT i. Goal – make recurring work as repeatable and deterministic as possible; standardize and automate Protect our deployment pipeline vi. Integrate our deployment activities with our change approval process vii. Reduce reliance on separation of duties 2. Ch. 22 – Information Security as Everyone’s Job

and when we realize that the costs and risks of custom development have been radically reduced, the economics often now favor custom development. Governance and Oversight: Governance has traditionally quickly and with more good information available.  “Failing” in this sense is simply an efficient process we use to select among alternatives. Shadow IT Agile ways of working support a community approach meet the needs of a part of the company, perhaps due to capacity constraints or to the governance process’s limitations. A picture of today’s emerging workforce. These characteristics of today’s emerging

feasible.  History – How I Got Here?  Contentious relationship existed between development and operations.  Left development because I was frustrated that it took so much time to get my products into production team wasn’t the same as the game time team.  Segregated technical and business functions  Development  Operations (Operational Waterfall)  Infrastructure Ops  Product Ops  Product Management related to product configuration and deployment  Built a strong relationship with development (built empathy)  Development began to see operational issues, and usability problems  The relationship is

when we have an annual schedule for software releases, where an entire year’s worth of code that Development has worked on is released to production deployment. Like in manufacturing, this large batch release 1. In the book Implementing Lean Software Development: From Concept to Cash, Mary and Tom Poppendieck describe waste and hardship in the software development stream as anything that causes delay for result. The following categories of waste and hardship come from Implementing Lean Software Development unless otherwise noted: a. Partially done work: b. Extra processes: c. Extra features: d.

details about Python 2 support in pip can be found at h�ps://pip.pypa.io/en/latest/development/release-process/#python-2- support pip 21.0 will remove support for this func�onality. #或者手动下载软件包并解压到以下路径： them. January 31, 2024 - 16:33:27 Django version 5.0.1, using se�ngs 'testapp.se�ngs' Star�ng development server at h�p://127.0.0.1:8000/ Quit the server with CTRL-BREAK. 以 上 命 令 启 动 一 个 web 服 务 器 ， 监 list(row) print(f"第{index}行: ", data) ★第16章、多进程与多线程 ★多进程mul�processing.Process类 python多进程（mul�-process）适用于计算密集型的任务， 对于I/O密集型任务应该使用多线程（mul�-thread），比如磁盘读写， 网络通信等 在python中，对于计算密集型任务，多进程占优势；对于IO密集型任

with processes in the Agile environment, which enables a more collaborative and productive review process.  Provide information to all key stakeholders on a consistent, regularly scheduled basis, either architecture is in place, systems engineers continue to refine it as they learn more from the development sprints and releases. Cost Estimation  Cost estimation in an Agile environment is challenging releases it can manage in a given year and the totality of delivered requirements within the entire development period of performance.  During the program execution phase, a high-level program estimate undergoes