The ongoing design and evolution of cyber-dojo
summary
A browser‑based practice environment that deliberately strips IDE features and enforces a 10-second test timeout, spins each run in a Docker container via a runner, and assembles language images with Travis CI then pushes them to Docker Hub. Files and test output are sent to microservices from a Rails front end, diffs for each traffic‑light step are stored and revertible, and anonymous multi-animal sessions support live peer reviews. A missing feature — round-tripping for generated files — is near completion (it previously lost approval‑style tests).
AI-written summary · about
chapters (10)
- 0:00cyber-dojo introduction
- 3:01Licensing and charity
- 4:45Architecture and stack
- 6:10Contributing and open source
- 7:58Handling framework updates
- 9:43Round-tripping limits
- 11:09Practice vs development mindset
- 13:54Framework suggestions
- 15:02Slow test insights
- 18:50Automated pipeline checks
related talks
33mThe Pivotal Engineering Dojo
27mHow browser IDEs are enabling the transition of development to the cloud
28mDev Tools to increase your speed that DON'T use AI
05mInstant Self-contained Development Environments
19mDevelop, Debug, Learn?
36mDojo: An Effective Implementation to Improve TDD Practice
45mContaining Your Development – Why Cloud IDEs Are the Future
50mInstant Self-contained Development Environments for Everyone