Inviting Code
summary
Claim: segment core from features so outsiders add plugins without core review; demonstrating a working Zagami metadata project used by Oxford and Cambridge, Python 3.4+ code, abstract base classes to enforce plugin interfaces, function annotations and PEP-0484 type hints for cascading validation, a plugin manager that safely loads and verifies modules, optional digital signatures and ACLs for plugins, and a custom importer that decrypts modules on the fly implemented and used successfully to prevent unsafe code from breaking the core.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:17Project complications
- 3:15Adding features willingly
- 4:02Creating a framework
- 4:35New features
- 5:52Documentation
- 7:05Product Segmentation
- 8:16Function Annotation
- 15:02Plugin Manager
- 15:58Abstract Classes
- 16:40Plugin Management
- 17:06Plugin Security
- 19:29Type hints
- 20:45Type Goons
- 22:10Conclusion
related talks
19mPowering Modularization at Airbnb: Plugin Architecture
01h 42mEverything is a plugin! Mastering webpack from the inside out
50mBuild Software Like a Bag of Marbles, Not a Castle of LEGO
45mPlugin Oriented Programming A New Way to Scale Development
30mExtensible Python: Robustness Through Addition
38mPlug-in Based Software Architecture for Robotics
31mForget Rebuilding, Install Plugins at Runtime
08mBreaking Barriers: Streamlining Backstage Adoption in E...