After that, viewers will have to put in some effort to mouse over your title to read past the cut. Something to keep in mind: Titles get truncated at about 40 or so characters. Succinct objective (Emphasis on singular!).What fancy technology I plan to use, if any.Unless you have an existing community, try to avoid low-value clickbait.Īs a lowly unknown I need to bring a simple, but descriptive stream title. Create loose structure to guide you 🔗 Write your title with intention 🔗 Pretty much no one is doing anything wholly unique, so I decided I would learn by copying what works for other coding streamers. I didn't want to reinvent the wheel, and so I had to experience what works for others and identify anything that is common.
I watched a few coding streams from people that I see in the space regularly prior to running my own. Set accurate expectations for yourself and potential viewers 🔗 Don't spend big money before you even have momentum. Terminal (I used Alacritty + the built-in terminal in VSCode).Condenser microphone (I use a Behringer C-1U).The following are the hardware + software I already had I’m running Linux on my System76 Gazelle laptop. My motivation for streaming my coding sessions is to improve my communication skills, as well as educate and demonstrate to others about being productive with programming languages and tech that I like using. There is much room for improvement, but I want to share what I used to get started. I used what I already had on hand, did not spend any money and I was able to stream for about 3 hours from zero code to a small completed project. A few people watched for a few minutes, so I considered it to be a success. I recently completed my first coding streaming session.
What I learned running a live programming Twitch stream from Linux
0 kommentar(er)
