▶ ▶ ▶ ▶ ## Tackling Technical Debt: Hello Junior Developers! CppCon 2021 Lightning Talks Tulio Paschoalin Leao – Software Engineering Manager October 28^{th}, 2021 cadence®  Photo by Robert Bye on Unsplash ## Key Concepts Technical Debt Resource Allocation “Free time” Junior Devs Senior Devs Knowledge ![Image](/uploads/d

2015Mike BallouNotes from Velocity1Chris KrullTechnical Humility1Jul 2015Jason WohlgemuthAgile software for Agile1Aug 2015Scott GrimesTechnical Debt2Michelle Bauer"Rapid Problem Solving with Post-It Notes Defense|2| |Jonathan Mowers|The Testing Pyramid with a focus on Unit Testing|2| |Scott Grimes|Technical Debt|2| |Nick Wenner|My Experience in Effective Retrospectives|2| |Sean Lomax|Scrum: The Art of Doing

# openEuler OS Technical Whitepaper Innovation Projects (June, 2023) Powered by TCPDF (www.tcpdf.org) ## CONTENTS 1 Introduction 001 Development Roadmap 002 2 Technology Ecosystem 003 Innovative pkgship 105 QuickIssue 106 Compatibility and Technical Assessment 107 OSV Technical Assessment 107 openEuler Compatibility List 108 openEuler Technical Assessment 110 Acknowledgment 111 ## 01 Introduction A new openEuler innovative version is released every 6 months to quickly integrate the latest technical achievements of openEuler and other communities. The innovative tech is first verified in the openEuler

PyArmor are written by c in the dynamic library _pytransform. _pytransform protects itself by JIT technical, and the obfuscated scripts is protected by _pytransform. On the other hand, the dynamic library it's not changed. This is called Cross Protection. The dynamic library _pytransform.so uses JIT technical to achieve two tasks: • Keep the des key used to encrypt python scripts from tracing by any c debugger

a4ce22604a2d29501c68ce28/p51_1.jpg) includes the C Rationale The ## Standard Incorporating Technical Corrigendum No.1 ## The value (time_t)(-1) is returned if the calendar time is not available ## in a consistent state, but it is a bug for a client to contradict itself ## Technical debt is quantifiable as financial debt ## As an evolving program is continually changed, its complexity, reflecting evolution Technical Debt is a wonderful metaphor developed by Ward Cunningham to help us think about this problem. Martin Fowler martinfowler.com/bliki/TechnicalDebt.html ## Like a financial debt, the technical

users and stakeholders monthly. These frequent iterations effectively measure progress, reduce technical and programmatic risk, and respond to feedback and changes more quickly than traditional methods operational and technical stakeholders. A product owner or a scrum master manages the backlogs, updating them based on the results of releases and sprints, changing operational priorities, or technical considerations software, to include software developers, database administrators and architects, testers, and other technical experts.| |End Users|Conveys operational concepts and requirements/needs, participates in continuous

Evolution Identify Technical Debt ## Code Reviews → Possibilities? What-If? Did you consider? Suggest Better ways Ask about Simplicity Remind about Evolution Identify Technical Debt ## Code Reviews Product Knowledge? Transactional involvement only Reviewer unaware of functionality Focus on technical aspects alone Mainly Ineffective ## Code Review → Innovation Too Late for idea exchanges At least about... Discuss & implement Better ways Ensure Simplicity Enable Evolution Address Technical Debt Evaluate more options! ## Pair Programming – Product Knowledge? High-Ownership Functional

actually degrade over time. 2. We improve daily work by explicitly reserving time to pay down technical debt, fix defects, and refactor and improve problematic areas of our code and environments—we do this actionable data within 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

Standards & Documents ## Software Development in Medical Devices 100+ Standards, Documents and Technical reports IEC 82304-1 – Health software IEC 62366-1 Usability ![Image](/uploads/documents/2/a/ wellness apps – Quality and reliability IEC TR 60601-4-5 Guidance and interpretation – Safety-related technical security specifications IEC 62443-4-1 Security for industrial automation and control systems – security hotspots are reviewed ✿ No new vulnerabilities are introduced ✓ New code has limited technical debt ✿ No new bugs are introduced ✓ New code has limited duplication Pre-Commit Hooks New code