Simpro Knowledge Base
This repository is a living wiki for building a high-performance engineering, product, and business culture.
It is written for CTOs, engineering leaders, product leaders, architects, delivery managers, designers, security champions, SREs, and team members who want to move beyond ceremonies into real ownership, measurable outcomes, continuous learning, and practical innovation.
Start Here
- Simpro Knowledge Base Home
- Simpro Knowledge Themes
- Operating Principles
- Team Culture Playbook
- Engineering Excellence
- AI, Local LLMs, and Edge Intelligence
- Annual Day Interactive Sessions - June 25
- Simpro Platform and Growth Engineering Stakeholder Brief
Browse As A Website
Open site/index.html in any browser.
To rebuild the browsable site after editing Markdown files:
python tools\build_static_site.py
Wiki Map
- 00 - Home
- 01 - Operating Principles
- 02 - Team Culture Playbook
- 03 - Engineering Excellence
- 04 - Software Development Methodologies
- 05 - AI, Local LLMs, and Edge Intelligence
- 06 - DevSecOps and SRE
- 07 - Design Thinking and Product Mindset
- 08 - Architecture and Technology Radar
- 09 - Leadership and Change Management
- 10 - Operating Strategy, Marketing, and Sales
- 11 - Learning System and Daily Research Rituals
- 12 - Annual Day Interactive Sessions - June 25
- 13 - Source Library
- 14 - Mobile App Blueprint
- 15 - Software Industry Evolution
- 16 - Integrated Simpro Operating System
- 17 - Industry Practices Playbook
- 18 - Book and Article Synthesis
- 19 - Visual Models
- 20 - Simpro Platform and Growth Engineering Stakeholder Brief
- 21 - Simpro Platform Engineering Foundation
- 22 - Simpro Growth Engineering Foundation
- 23 - Simpro 90-Day Platform and Growth Roadmap
- 24 - Simpro Platform Tooling and Environment Lab
- 25 - Simpro Book Synthesis: Platform Engineering and Growth Engineering
- 26 - Facilitator Explanations And Visual Learning Guide
- 27 - Storytelling And Gamified Learning Journey
- 28 - Team Quest Catalog
- 29 - Expanded Concepts Through Story Cards
- 30 - Gamified Annual Day And Team Workshop Formats
- 31 - Simpro Field Guide Home
- 32 - Simpro Operating System
- 33 - Industry Transformation Stories
- 34 - Small Company To Market Leader Playbook
- 35 - Strong Foundations For Scale
- 36 - Reusable Platform Strategy
- 37 - Growth Engineering Strategy
- 38 - Simpro Technology Review Dashboard And Rituals
- 39 - Adoption Plan For Simpro
- 40 - Learning Retention System
- 41 - Developer Help Home
- 42 - VS Code Cheatsheet
- 43 - Git Cheatsheet
- 44 - PowerShell And Bash Cheatsheet
- 45 - .NET CLI Cheatsheet
- 46 - Docker And Podman Cheatsheet
- 47 - Kubernetes Local Clusters Cheatsheet
- 48 - Python Environment Cheatsheet
- 49 - Agile Scrum Kanban Cheatsheet
- 50 - Simpro Engineering Fundamentals Playbook
- 51 - Evolution Of Software Design
- 52 - Design And Architecture For Developers
- 53 - On-Premise And Cloud Architecture Fundamentals
- 54 - System Design Patterns Cheatsheet
- 55 - Generative AI Across Software Delivery
- 56 - Agentic AI For Platform And Growth Engineering
- 57 - Frontend Technology Choice Guide
- 58 - Micro Frontends And Monorepos
- 59 - .NET, C#, And ASP.NET Good Practices
- 60 - Python Project Good Practices
- 61 - TypeScript, JavaScript, React, And Angular Practices
- 62 - Simpro Security Learning Path
- 63 - Secure Development Lifecycle
- 64 - Defense In Depth And Zero Trust
- 65 - Threat Modeling And Risk Analysis
- 66 - Security Testing Tools And Practices
- 67 - OWASP Developer Security Guide
- 68 - Encryption, TLS, Certificates, And PKI
- 69 - Human Side Of Security
- 70 - Software Security Standards And Certifications
- 71 - Performance, Reliability, Scalability, High Availability, And Cost Learning Path
- 72 - Performance Engineering Guide
- 73 - Reliability Engineering And SLOs
- 74 - Scalability And High Availability
- 75 - Cost Control And FinOps
- 76 - Observability, Capacity, And Operational Readiness
- 77 - Daily Engineering Hygiene Standard
- 78 - Simpro Knowledge Themes
- Simpro Stakeholder Deck Outline
- Templates
How To Use This Repo
- Treat the wiki as a working agreement, not a poster.
- Every team should translate the principles into visible habits, dashboards, checklists, and review cadences.
- Update pages when learning changes. A stale knowledge base teaches people that knowledge is decorative.
- Use pull requests for changes that alter team standards, operating rituals, or recommended practices.