CI
Continuous integration; automated test/build pipelines that run when code changes, which Steinberger runs locally rather than relying on GitHub's.
As defined in Lex Fridman Podcast #491 - OpenClaw
Where it comes up · 2
- George Hotz #32 claims
- Lex Fridman Podcast #491 - OpenClaw1 claim
Most important claims · 3 of 3Search all claims for “CI” →
- The closer it is to true that changing the code and passing the tests means you didn't break the code, the more you trust your tests and the faster you can make progress — which is why Comma and tinygrad invest enormously in test coverage so a passing pull request can be merged confidently.George Hotz #3
- A legacy code base like Twitter's needs refactors before features: you first build trusted tests/CI before touching code, then replace old modules with simpler ones (e.g. 100k lines replaceable by 300 lines of Go), and Hotz believes 50 people could comfortably build and maintain Twitter — the code base grew because engineers get promoted for adding libraries others use, not for simplicity.George Hotz #3
- Rather than rolling back when something goes wrong, you should move forward and ask the agent to fix it, and refactors are now cheap because modern agents will just figure things out, so you can commit to main with local CI when tests pass instead of perfecting prompts and reverting.Lex Fridman Podcast #491 - OpenClaw