*Summary:* - define the *core* mechanics of your application - this is really important - if you are to 1) finish your prototype fast and 2) have it realistically represent your vision, you have to ensure that you define the *core* mechanics and only the core mechanics - when working (coding, designing, etc) keep focused on the core mechanics at all times (avoid "urgent" things that pop up) - follow a process (helps you keep focused on the core mechanics) - he recommends the design sprint process - most important thing: experience building an app in 24 hours (or a few days) a couple of times, what you learn from the experience will be far greater than watching any video or reading any book on fast prototyping. Thanks so much for the talk! I really enjoyed it! Great presentation!

Sorry about the audio on this everybody, I feel like it really diminishes the work I put into this talk. What is that noise? It is most likely caused by too much compression in mixing. Compression amplifies low audio levels and limits high ones, so it's used in situations where speakers can be varying distances away from the mic and might have different speaking volumes. This way you always hear what the speakers are saying, at a predictable volume level... The tongue smacking sound you hear throughout the entire speech is mostly due to lazy audio engineering & bad compression management.

This is one of the most practical talks I've ever seen. Holy crap. Real relatable information that both inspires and informs. Very well done.

great talk, not just for game dev but project management in general

Excellent yet simplified process. For a novice to game design, this made it so clear how to approach prototyping

The most difficult thing about prototyping is deciding which directions to focus on in your MVP in order to be able to test it properly. For example - if you were building an Angry Birds prototype, which parts could you skip without making it lose it's appeal? Would it be fun without physics? With bland placeholders instead of art? With just 1 level?

Fantastic rundown of a clear process

Thank you so much for this valuable talk!

"The impediment to action advances action. What stands in the way becomes the way"

Great Talk! Thanks Mark!

Water is right THERE! Seriously, good talk, I would be to scared to even go on stage

Drinkkkkkkkkkk it man! good for both of us.

This is golden. The audio issues aren't the speakers fault. Shit compression to blame

Really great talk. Thank you.

What an ASMR talk...

I went out to drink 4 times during listening to him in the hopes that he'll take a sip as well. He didn't :(

bit sensitive mic, but so far a pretty good talk :3

Crazy good talk

Great talk!

Really good!

Very inspiring

Neat! Thanks!

Anyone is here to get ready for a game jam? GMTK 2020 maybe ?

Thank you

There is a lot of mouth sounds in this one

I do rapid prototyping but the biggest problem is how to analyze the results. If something is not popular right away, how do you distinguish between if it's a bad idea or just needs more polish? Cause many ideas will not be interesting until they reach a certain level.

I really liked the talk, super informative and insightful. But is someone smacking their lips the entire time next to the mic?

14:48 -- "when he made this he had no job ... used crappy equipment that no one else knew existed in the school where he was working"

This is too meta for me, somebody please translate it to bro-speak so I can understand!

I put in top_favorites list. Thanks

17:49 Didn't make sense not to live for fun!

thanks gaming Nicholas Cage C:

Don Hertzfeldt, nice.

I keep coming back to this video because of the title... and because I can't listen to more than 90 seconds of his dry lips.

please gdc, get a pop filter on that mic up there

0:22 check, check aaaand check!

Yo is that a metallic toad in the thumbnail?

He sure knows how to make us engaged

I wish I could find Game Jams in Charlotte NC. Anyone know any?

It sounds like there's Pop Rocks in his mouth.

Good talk, but could have cut out the majority of the motivational speaker but in favour of case studies and tips on prototyping.

The problem with that classic prototyping analogy "1. bike 2. motorbike 3. car” rather than ”1. wheels 2. chassi 3. car" is that you have to spend time building handlebars for a bike, and less time on your end goal.

Where can i find the boy or girl game to play?

Carefully avoiding putting out a fire by avoiding the immediate impulse to take a sip of water. I really wanted to listen to this video, but I can't.

This is like a class from Klaus in Umbrella Academy

the entire time i was watching the water bottle, hoping he'd take a sip so I could listen to the talk without hearing his mouth noises.

14:48 "No job" 14:58 "School where he was working". Checks out.

Yeah an MVP is not a prototype it's more like what we used to call a "first playable"... prototyping will not guarantee any viability, or for that matter be even a product and that should be ok, iterate and try again or move on... month prototype is rapid?

Considering the overwhelmingly positive comments, does anyone really find this idealistic approach to work at all? Like sure, if you already have a large successful company and want to optimize the processes, it surely does help, but isn't the high-level overview of how you should plan things just impossible if you aren't already an expert? Scrum surely is a good process, but how just saying "use scrum" help anyone? The hardest part is actually learning the things from implementation standpoint, getting educated in drawing and properly using the tools, having several years of experience in marketing to know what sells and what's just another copy of what people made thousands of times... Like for example if you want to implement something in a game engine, even though you can tell yourself that you'll do it on few hours, but you may learn that there's a bug, improper documentation, or that your approach doesn't make sense at all, and you'll be lucky if you succeed in a week; plus you may learn that it makes no sense to continue until you learn something new that may make the rest of the development way easier (or even possible at all), so you can be constantly fighting the dilemma of whether to spend time on actually improving your skills, or trying to implement a workaround asap. And if you can make something in 30 days that a pro would do in one afternoon, because he doesn't repeat the mistakes anymore, doesn't it become a mere training exercise? Instead of being a "business model"? Shouldn't learning be an ever-increasing necessity in our world of rising complexity, where plans or schedules often make no any sense at all (until your processes are already flawless, which should be the goal anyway), because you can't predict how long it'll take to learn something? I mean don't get me wrong, if you specialize or just get educated before starting to make the game, the tips are definitely worth something, plus you usually don't start from scratch. Nevertheless, I don't like how this high level presentation tries to convey the oversimplified idea, which most people may definitely misunderstand. And on the other hand, for those who are actually experienced, tips like "use agile methodology" should be absolutely obvious by now, this isn't a year 2000. I mean, all I'm saying is that this presentation lacks any useful specific examples of day-to-day issues, along with not presenting any metrics to prove and specify who does this apply to.

I'm eight minutes in and so far it's been all waffle.

I'm sure what this guy is trying to say is very helpful. But the way he is saying it is not very relatable or personal. It's very "pseudo" proffesional, meaning it got all these points and diagrams that no one is gonna remember or want to cognitively understand. And the examples he gives doesn't help explain anything. This guy just spent 25 minutes saying, you need goals!

Great talk!