The journey from home-brew analysis scripts to a product
summary
Starts with a working Python/Matlab analysis and turns it into a SaaS that actually runs at scale: a simulation engine packaged for customers as ChargeSim with a React frontend calling AWS Lambda and API Gateway into a Docker container on Fargate. Covers authentication (Cognito/JWT), schemas and type hints to stop user-input bugs, structured error codes and logging, documentation-as-part-of-feature work, and how a correct layout changes costs by about twenty thousand euro a month for a 100‑bus example.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:30From scripts to product
- 3:18Architecting SaaS tool
- 5:05Scripts versus products
- 7:09User expectations and requirements
- 8:32Security: auth and authz
- 10:20Authentication solutions
- 11:42Authorization complexities
- 13:28JWT tokens for auth
- 15:57Documentation as a critical product component
- 18:04Building robust system
- 19:28Static typing and schemas
- 21:13API validation with Swagger
- 22:18Handling errors and feedback
- 24:04Error tracking and management
- 26:13Conclusion and key takeaways
- 27:15Q&A
related talks
28mThe hidden infrastructure powering our frontends
28mA Modern Application Builder’s Guide to Testing
28mA Modern Application Builder’s Guide to Testing
54mScaling Web Services for Free to Play
50mThe API Product Management journey: a simulation
17mBuilding a culture of curiosity at your company
13mTurbocharging your Developer Ecosystem
32mSoftware development reimagined