Stream in 1080p, its the perfect balance between text looking ok and everyone being able to view it well with their internet connection.
There's also longer term goals like Handmade Hero on YouTube. Think about some long term 2 year project and start making it. Make the next Spotify or PUBG. While that being successful would be equally nice, the channel could also be the more successful item.
Next time I do it, I'm going to have a separate account on my machine, where I will avoid having anything accessible that is sensitive.
https://medium.freecodecamp.org/lessons-from-my-first-year-o...
The things that I’ve settled into when streaming that I tack onto that wisdom: -stream for at least 2-3 hours per session
-always double check your mic, I forget to unmute.
-downmix your mic to ensure you’re heard evenly
-noise gate and noise suppression are a must
-run obs on your pc but stream all of the code itself from vms. This solves most privacy problems and spares a lot of the common obs-on-screen issues you’ll see during streams. Also makes it easier to transition
-MAKE YOUR FONT BIGGER
-pay attention to chat! I’ve got 1440p monitors, so I keep my 1080p vm on the main screen and my chat / todo list stays on that as well
-set up notifications with stream labs (they’re fun and make people follow in cascades)
-pick reasonable stream titles. I’ve lost pretty much all of my viewers one stream due to a bad title
-consistency is king
-if you’re expecting undesirables, aggressively configure nightbot. Defaults and twitches built in mods will not be sufficient and white Supremecists will get around those settings easily.
I haven’t chosen to do a webcam but I know streamers can pull high enough views without them, so it’s just up to you and how consistent you want to be. I can share more of my experience if you like.
Twitch coding is the best and it prepares you for pair programming and whiteboard interviews where you have to talk while thinking through a problem.
I'd love to hear your perspectives! I understand streaming in gaming contexts, developer streaming is new to me.
Also I enjoy hearing other people code, especially the clack of the keyboard.
I remember there were some internet radio streams that had office sounds playing (at different intensities), but I do not think they're online anymore.
I also find it relaxing to hear him talk, while me doing something else at the same time, like playing a game of Civ.
---
[0]: https://www.youtube.com/channel/UCCuoqzrsHlwv1YyPKLuMDUQ
I'm fairly new to dev, and my colleague is even newer. The sysadmins only know PowerShell, so I'm always teaching myself, and don't get to pick up on best practises or learn how anyone else would do things, other than from what I read online.
I guess it'd just be cool to see something built from start to finish, watching the problems they encounter and how they work around them.
I view every livestream I watch as a one sided code review and refactoring session, and spend most of the time watching reasoning through how they are coding and if there are things that could be clearer. I learn lots from that... including new idioms that I like or despise.
I’ll also watch streams where the coder needs help, so I’ll pitch in over chat to help with problems. I’ve taught several people suprising amounts through twitch chat and despite twitch delay.
Just try watching a stream or two! Check the creative communities on twitch and select programming or game development!
Maybe have an obvious ?autoplay=true param.
My wish-list:
A good chat API which supports code snippets (this is something that streamers will want to pour over and make streams about, because it makes good content!).
Localized streaming servers in order to keep latency low.
The site development process should be streamed! I have no idea why the Livecoding guys didn't live stream their dev work (other than perhaps a fear of losing "IP", but I personally don't think that's a particularly strong argument - there's always some code that could be streamed without issue, such as frontend JS. I suspect the real reason was that their developers weren't aligned with the product and didn't want to stream).
Support for pair programming (two streamers working on the same project together) - this allows streamers to market to each others' audience, and can produce some really great content as the streamer is forced to explain to their partner why they're doing what they're doing.
Integration with editors as an alternative to regular streaming. A UI which looks something like jsbin.com - where the text editor is shown next to the output - would allow for streamers with lower upload speeds to only stream their webcam, while their editor and terminal is mirrored in text, nicely resizing to fit the users' screens. This view could be composited into a video stream for users who aren't viewing through a web browser (like chromecast users).
Things like storing VODs (videos of past streams), community tooling, etc., are hard and EXPENSIVE. The developers have a very hard path ahead of them.
The tech behind 9 out of 10 tech startups is relatively trivial to clone. The part that's really hard to copy successfully is the people.
It's also worth noting that if you can't do the people bit then even the most brilliant, un-cloneable tech is likely to fail. It's very hard to get customers if people don't like you as a person.
But hey, that's what co-founders are for.
Greg is building a product on top of Ruby/Rails. You might find this interesting.
As a practical point the text on the stream thumbnails is strangely half-translated which looks odd on an otherwise English-using page.
An idea: it would be cool to have separate feeds for the available tags so that users could browse the available streams/channels by topic.
Good luck for your project!
