We’ve got another big, 2-hour episode of the podcast for your listening pleasure this month!
In addition to our usual wrap of all the games coming out this month, we chat about a lack of understanding about how games get made and published. This is of course in response to the GTA VI leaks from a few weeks ago, but it does seem to be a timeless topic – why do people not better learn about how games are made?
And then we also chat about a favourite genre of ours at DDNet – the rhythm game genre! What are its strengths and weaknesses as a genre, and how awesome is this new tuba-playing rhythm game that is doing the rounds right now?
Thanks as always for tuning in everyone and let us know your own thoughts on this episode’s topics!
The podcast is completely free, and there are a couple of ways that you can listen in:
1) Download the free Podbean application, and subscribe to the Digitally Uploaded podcast there (Just search “Digitally Uploaded”). Alternatively, you can find us through our Feed RSS, here: https://www.digitallydownloaded.net/feed
2) Simply head on over to the Digitally Uploaded mini-website and follow us there. You’ll be able to download episodes that way too to listen to them offline: http://digitallydownloaded.podbean.com/
3) Simply click on the player below to tune in as you browse DDNet!
4) We’re also on iTunes podcasts, which you can find here. Or Google Podcasts, which you can reach by clicking right here! Or Amazon’s Audible! We’re on there too! Click here.
Enjoy, and as always, please do let us know if you’ve got any feedback or would like for us to discuss a particular topic on an upcoming show.
I didn’t listen yet but as a rule, you should never find out how your favourite things are made. The more I know about how movies are made, the more the magic disapates and the more I get to know how wrestling works the more holes I can poke in it.
When you have a listen you’ll understand the context of what we’re talking about better. It’s not so much that you need to know how the sausage is made just because, but it was more the people that are absolutely convinced that they can tell game developers how to do their jobs, despite clearly having no idea how games are made, that are being a bit silly.
The title of this and also your newer post is very misleading in my opinion. You see, it’s not not knowing how something is made that’s the issue. It’s not knowing and thinking or pretending that you do. It’s like people using the “you’re so ignorant” argument to a certain comment. Ignorance isn’t a problem. After all, it just means a lack of knowledge. But a single person can’t know everything.
In short, I can see myself in the content of your arguments here but I resent how you present it.