|
|
|
|
|
by gertlex
262 days ago
|
|
Thought at first this was maybe just being applied to external product demos, but this reads like dev demos, too: > Since most of the time you're demoing something you previously worked on, this prevents you from working on current stuff right up to the demo, because you're worried you might break your local setup for the demo by installing different node modules, switching to different Git branches, etc. This isn't the case for me generally... probably more of problem for web-apps things I guess. I keep multiple workspaces locally for the multiple things I'm working on, but that hasn't been my pain point. Usually it's that I'm demoing a work in progress (not my choice generally) that has rough edges. I enjoy the internal demos where questions can be asked about doing XYZ, and that can be shown if it's quick. Recordings tend to take away from that, and be less memorable/engaging I guess. |
|