Live Coding
summary
Live coding uses a commit-per-change workflow: every edit becomes a git commit that gets reloaded, driven by a small script that stitches files into a commit sequence instead of manual checkouts. It runs compiled examples automatically (no manual compile) and mostly works, but larger-than-minimal commits and losing track of the next change cause confusion. The demo uses a hacked repo plus a macro to switch commits; suggested improvement is editor integration (e.g. VS Code highlight of git show).
AI-written summary · about
chapters (9)
- 0:00Start
- 0:02Bloomberg Engineering
- 0:14Code On Slide?
- 0:28Weekly Mob Programming
- 1:17each change a commit
- 1:30alias/macro to switch commits
- 1:44Build from sequence of files
- 2:18Problem: what changed...?!?
- 2:57typing would slow down
related talks
01h 22mGit-ting along with others
01h 29mBetter Code and Collaboration through Open Source Concepts, Dev Containers....
27mTaking code to next level with Open Source (Git & Github)
19m20 mins to git comfortable
44mGit, Dammit!
43mDesigning in code
25mTurning codebases into conversations
30mLearn how to never commit $%@ to Git