Low-Code Meets Public Code: Automating
summary
Claim: combining low-code platforms with public code cuts delivery time and raises transparency. A global bank shrinks a compliance project that used 20 developers for six months into eight weeks with a five-developer + five-analyst hybrid team; a hospital cuts patient admission time by 30%. Typical savings: 50–90% development time, up to 30% government IT budget via reuse. Practical stack includes API-first + CI/CD (Jenkins, GitHub Actions), versioned low-code artifacts, automated tests, security scans and RBAC-backed governance.
AI-written summary · about
chapters (10)
- 0:00Introduction and Welcome
- 0:34The Need for Change in Software Delivery
- 2:23Understanding Low Code
- 3:08Exploring Public Code
- 3:52Architectural Patterns for Integration
- 4:51Governance and Standards
- 5:41Real-World Integration Practices
- 6:30Sector-Specific Case Studies
- 7:17Challenges and Pitfalls
- 7:55Future Directions and Conclusion
related talks
23mPublic Sector: Stories to Getting Started
45mAn Open Source Approach to Driving Developer Efficiency
08mLow-Code + Open Source = Appsmith
28mUnlocking Agility with Open Source: A Guide for Modern Businesses
05mHow the Standard for Public Code can help you collaborate over time & space
30mRegulation Innovation - Stories from the Trenches Panel
32mFreeing software with governance, for public administrations
01h 09mMaking Government 2.0 a Reality: A Citizen's Guide to Essential Reforms