(no title)
Adam13531 | 6 years ago
> How was streaming development of the game?
It was great! People ask me a lot about what I'd change if I could go back in time or start again, and while I would certainly change some technological decisions, I would not change the streaming aspect. There are so many great things that have happened over the years, and I feel like the culmination of all of it can be summed up in this launch-day highlight I took: https://www.twitch.tv/videos/486320333
That one video felt like it made the whole journey worth it.
> Are you concerned about your source being visible?
I wasn't super concerned for a few reasons:
• Code is copyrighted as soon as you write it, so if someone were to take it, I would be able to take legal action against them.
• Perhaps more importantly, I didn't think anyone would want to copy Bot Land's code. Automation games are growing as a genre, but rarely will they include scripting as the main component. To my knowledge, there wasn't a scripting-based game ~4-5 years ago that proved that they could be successful.
• See the next answer...
> Or feeling like you are being watched or judged while coding?
Impostor Syndrome runs rampant with coders. Did I feel like I'd be judged? Yes. Was I? 100% yes (by some people). Were some people mean about it? You'd better believe it. However, I started streaming for accountability and marketing, and I wouldn't have gotten those benefits if I didn't stick with it.
Also, remember that as a streamer, you control who gets to stay around in your chat. People are entitled to their own opinions, but I think the #1 rule as a streamer is that of entertainment: the show must go on. As a programming streamer, this doesn't mean that you have to be entertaining all of the time since you have to be productive while streaming. Either way, in order to keep the show moving, you have to be in a good enough mood to do things. When a troll gets in the way of that, you purge/timeout/ban and move on.
If someone is judging you for your coding style or standards in an unconstructive way, you have tools at your disposal to handle it.
> When did you start streaming development?
I started on September 8th, 2015. I believe I had one follower on Twitch at the time, a real-life friend of mine.
> I'm worried my side project is too early in development to stream...
I don't think anything is really off-limits for a development stream. I've spent entire days streaming myself milling around entirely in a text document (i.e. not even code). I've spent days writing automated tests, triaging bugs, debugging, etc.
> Did you end up having to spend a bunch of time making extra stuff for your audience, like the faq you linked?
Yes. If I had to estimate how many full work days I've put into just streaming-related tasks, I would say it's about 10-15. Granted, you can just start with practically no preparation and see where it takes you, but I don't advise doing that. My advice on streaming hasn't changed too much in the past years; it's mostly encapsulated here: https://blog.bot.land/2016/10/being-a-development-streamer-o...
Streaming is just as saturated as games are nowadays. There are a million streamers trying to make it big who "don't care about the numbers, they're just doing it for themselves". If you want to get started, I'd say that you should come up with a goal pretty early on, and that goal should not be to earn money from the stream. I won't share exact numbers, but I make less than minimum wage as a streamer. As a developer at a traditional job (in the U.S.), I'd make plenty of money.
I'd be happy to answer more questions you may have, although I think you'll have to see for yourself how streaming goes in order to consider whether it's worth it. And be ready to come to the conclusion that it's not worth it since it can affect your productivity and possibly your mood/energy.
Pfhreak|6 years ago
Do you find it difficult to converse with folks while programming? How do you maintain flow state while streaming? (Maybe this is just a skill you pick up?)
Adam13531|6 years ago
This comic (which you've probably seen!) sums up context-switching as a programmer: https://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt...
Imagine that but multiplied by 100. Every 3 seconds, someone is saying something that you can see out of the periphery of your vision. How difficult it is to interact is up to you; you can hold off on chat and handle it every X minutes, you can let them interact with themselves, or you can interrupt your flow every few seconds.
I try to take extensive notes about what I'm doing at any given moment so that I can always pop the context back off the stack and resume my work. It's a skill you'll hone as you go.