3 ms·
1. Stop 2. Just use a part of your screen that is off the recording. Never open `.` files on the stream. Never login on the screen, always off of the screen. If
by avitzurel 9y ago
1. Stop
2. Just use a part of your screen that is off the recording. Never open `.` files on the stream.
Never login on the screen, always off of the screen. If you are showing AWS cli console stuff, make sure you hide the public IPs and public DNS of things.
- Kiro 9y ago2 is related to 1 - there are credentials hard coded all over the place.
- avitzurel 9y agoso stream another project. As a habit, I don't stream code related to my workplace, it has too many risks. Even if you see parts and pieces and will not be able to make sense of it. We don't have a single secret embedded in code and all of our secret files are encrypted using vault, even that is too risky for the clients we have. I stream my personal projects and things like QnA etc...
- striking 9y agoClean up your code before you start. Maybe this exercise will make you a better programmer.
- mdmnk 9y agoI do this sometimes -- however I also think that cleaning code on stream is even more beneficial. Teaches you to code under pressure and scrutinize your code more-so than when you're alone sometimes. Also its fun for people to see how to reduce 30 lines to 5 etc.