Re:Lessons from my first year of live coding on Twitch
by nightcracker on Friday July 07, 2017 @05:02PM
(#14722068)
If you are programming, especially in a live studio environment, you should really invest into multiple monitors.
[ Parent
| on HN ]
Re:Lessons from my first year of live coding on Twitch
by ekimekim on Friday July 07, 2017 @05:21PM
(#14722219)
The author mentioned several times that they tried a second monitor, and it just wasn't their thing. And that's ok.
Everyone has different preferences and something that works great for you (and me - I have a 4-monitor setup right now and loving it) isn't necessarily what works great for everyone.
Re:Lessons from my first year of live coding on Twitch
by Tarq0n on Saturday July 08, 2017 @08:40AM
(#14725213)
The author tried a laptop monitor, that's much less ideal than a second monitor bordering perfectly of the first.
Either way it will definitely challenge your multitasking though.
Re:Lessons from my first year of live coding on Twitch
by to3m on Friday July 07, 2017 @07:33PM
(#14723071)
I've never watched this particular stream, but I've watched a few others. I expect many (most?) people are like me: they watch the stream on their TV while doing something else, or they stick it in a corner of their desktop, or on a spare monitor, ditto. Either way, if you go much past 1080p - at least for the region that's being streamed - it stands a fair chance of being hard to read.
(If you use a single monitor for coding in the privacy of your own home... well... what can I say? It takes all sorts.)
Re:Lessons from my first year of live coding on Twitch
by elif on Friday July 07, 2017 @05:54PM
(#14722462)
if you're trying to present to viewers, two monitors will make keeping them focused into a ridiculous chore.
That is like telling a speaker to prepare two slide decks and switch between them during the talk.
Re:Lessons from my first year of live coding on Twitch
by minimaxir on Friday July 07, 2017 @06:54PM
(#14722859)
Using a second monitor for live streaming is more useful for things useful to the streamer but which do not need to be shown on screen to readers (e.g. frantic Stack Overflow research when the code breaks, or analytics as the article mentions).
Re:Lessons from my first year of live coding on Twitch
by memco on Friday July 07, 2017 @08:35PM
(#14723375)
While it may not work for everyone, Casey Muratori (of the Handmade Hero referenced in the article) shows pretty much his whole desktop, including the times he is looking up documentation. Granted, he's not searching SO, but actual API documentation for Windows OpenGL or CPU instructions, he goes through his whole thought process including the time and effort it takes to understand and interpret documentation.
Then again, he also doesn't interact with chat at all while programming and only looks back at the end and answers questions afterward. So he breaks a few pieces of advice others might say are essential for a stream.
Re:Lessons from my first year of live coding on Twitch
by noopkat on Friday July 07, 2017 @08:59PM
(#14723446)
I think showing your process is really important and helpful to those watching your stream. I always show what I'm looking up in my browser. Folks at home are really great at helping me read it, as I'm often talking while trying to skim the docs quickly - not a good combination!
Re:Lessons from my first year of live coding on Twitch
by oneeyedpigeon on Friday July 07, 2017 @06:42PM
(#14722785)
I don't know much about streaming, but having watched lots of twitch channels, I think some streamers use one screen for stream display, and the other for everything they want to see but don't want the viewers to see e.g. chat, sensitive stuff, etc.
Re:Lessons from my first year of live coding on Twitch
by ue_ on Friday July 07, 2017 @06:47PM
(#14722822)
That's exactly what I do when streaming Overwatch, especially when my friend talks to me via IRC and I reply with voice. That said my monitor is big enough to have both the game and IRC visible, and I could set OBS just to record the game.