Q: How long have you been working on this project? 🐱

Summary

In this engaging script, Peter recounts his journey with a game development project that began with a simple walk cycle animation during a flight home from GDC. Initially a weekend hobby, it evolved into a full-time endeavor starting around August or September. Peter discusses the challenges of solo development, such as getting stuck in thought processes without team feedback. He also mentions using live streams as a means of self-reflection, akin to using a 'rubber duck' for debugging. With a goal to ship a short game by January, Peter is currently focused on refining gameplay and planning future levels.

Takeaways

• 😀 Peter started working on the project in May, creating a simple walk cycle animation during a flight back from GDC.
• 🛫 The initial project was a small, casual endeavor done during weekends, with the first gameplay dating back to May or June.
• 🔧 Since around September, Peter has been working on the project full-time, with periods of rapid progress and occasional slowdowns.
• 🤔 Peter sometimes gets stuck in 'swamps of thinking too much,' indicating moments of over-analysis and rebuilding within the project.
• 📈 The project's speed fluctuates, with Peter attributing some of the progress to working with others, who act as 'rubber ducks' to help him think through issues.
• 💬 Peter mentions using live streams as a modern version of the 'rubber duck' debugging method, even if there's no active commentary from viewers.
• 🎮 He aims to ship a short game by January, focusing on getting everything to work as desired before moving on to additional levels.
• 🔄 Peter is revisiting the first level to rework some elements, indicating an iterative development process.
• 🗣️ Peter considers talking to himself, like Peter suggests, as a method to overcome getting stuck during solo work.
• 🎥 The transcript reveals a candid insight into Peter's development process, struggles with solo work, and the use of external inputs for problem-solving.

Q & A

When did the speaker start working on their project?

The speaker started working on their project in May, as they were on a plane home from GDC and began experimenting with Odin and rail Li.

What was the initial activity the speaker engaged in for the project?

The speaker created a simple walk cycle with a cat character using pixel art on a Sprite during their flight home.

How did the speaker describe their project's progression over time?

The project started as a small weekend activity but has since grown into a full-time endeavor since around September or August.

What is the speaker's current work pace on the project?

The speaker's work pace varies, sometimes moving quickly and other times getting stuck in 'swamps' of overthinking and rebuilding.

What challenges does the speaker face when working alone on the project?

The speaker finds it difficult to get unstuck when overthinking or working in a suboptimal way without the presence of team members to provide feedback.

How does the speaker use streaming as part of their work process?

The speaker uses streaming as a method to explain their work, which serves as a form of 'rubber duck' debugging, even if there are no active comments from viewers.

What is the speaker's goal for the project?

The speaker aims to ship a short game by January and is currently focused on getting all aspects of the game to work as desired.

What is the speaker's approach to dealing with being stuck on the project?

The speaker has considered talking to themselves or using a microphone to verbalize their thoughts, similar to the 'rubber duck' debugging method.

How does the speaker describe the unexpected benefit of streaming their work?

The speaker initially used streaming as a personal debugging tool but found that viewers also provided valuable questions and feedback.

What is the speaker's current focus in terms of game development?

The speaker is working on getting the first level of the game to a satisfactory state before moving on to additional levels.

What does the speaker mean by 'rubber ducks' in the context of their work?

The term 'rubber ducks' refers to a debugging technique where explaining a problem to an inanimate object, like a rubber duck, helps to clarify one's thoughts and identify issues.