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.

2 is related to 1 - there are credentials hard coded all over the place.

Clean up your code before you start.

Maybe this exercise will make you a better programmer.

I 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.

so 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...

Concerning 1: My code is regularly horrible. I start any project in pure prototype mode. How quickly can I get what I want on-screen and working, so I can figure out if I actually like it enough to keep going in that direction? Once I'm out of proof of concept mode, I start working on things properly, and inevitably some horrible prototype implementation of something will survive for several months. It's always entertaining to anyone else in the room when I stumble on this, and loudly exclaim "Dear god, what was I thinking," usually followed by inquiries, explanations, and humility. Bonus points if my old code is the source of some mysterious problem that is now solved. :)

Concerning 2: I would never code something actually sensitive on twitch. Fortunately I enjoy programming video games, so I can stream that with relative safety, but I wouldn't ever stream something from my real job for example.

> My code is regularly horrible. I start any project in pure prototype mode

This is my preferred method of programming as well -- start with a pile of working crap and refine. order out of chaos!

1: your code will improve. don't be afraid of your bad code, other people are probably at your level or worse. You can use this as a learning experience. take the good advice given in chat and ignore the trolls.

2: dual boot / set up an account on your system that doesn't contain sensitive stuff.