Stop acting like a hobbyist gamedev

Summary

The speaker argues that independent game developers should shift from a hobbyist mindset to a professional, execution-focused approach. The central idea is that momentum is often worth more than small cost savings: spending modestly to remove a bottleneck can help a team keep developing, hit milestones, and release sooner.

Key Frameworks and Playbooks

Protect Development Momentum

• Prefer short projects—roughly 2–4 months—when possible. They are easier to keep moving than projects planned to take a year.
• Break longer projects into visible milestones spaced about 2–3 weeks apart. Each milestone gives the team a near-term target and a reason to keep pushing.
• Avoid long periods with little visible progress. They can weaken team energy and make it harder to recover the project’s pace.

Evaluate Spending by Opportunity Cost

Compare a purchase’s cost with the time and potential revenue lost by delaying work. The speaker’s example is a $40 asset: waiting for a sale might save $20, but could cost two or three weeks of development momentum.

The recommendation is not to spend indiscriminately, but to invest when a purchase is likely to save time or improve execution.

Set Ambitious Goals and Operate Accordingly

Big goals can help teams prioritize and sustain effort. Byte Me’s stated ambition is to become a million-dollar studio.

The speaker recommends treating even a solo or part-time project professionally: plan, set goals, and make decisions as though running a real studio. They also recommend having meaningful motivators beyond personal rewards, including responsibilities and relationships with other people.

Solve Problems Instead of Worrying

Ask: Is there a problem? Can I do something about it?

If the problem is actionable, take the next step. If it is not, worrying will not help. The speaker frames most game-development challenges—including performance, design uncertainty, and marketing—as solvable, though they may require time and effort.

Examples and Operating Lessons

• Desktop Island: The game experienced repeated delays after an intended March/April release plan. The speaker says its extended development period—around 11 months—hurt momentum, energy, and the sense of visible progress.
• Silicon Architect: Momentum improved when work was organized around successive milestones: a demo launch, the Osaka Indie Game Summit, and Steam Next Fest. Further goals included a substantial demo update and potentially a second creator campaign or a release-date announcement.
• M198: The team maintained daily momentum from development through release, completing the game in about 100 days. The speaker says the team generally worked six days a week, sometimes seven. Seeing the game evolve rapidly made the work more enjoyable and easier to sustain.
• Team equipment: Byte Me considered a roughly €4,400 MacBook for Thomas. Although a cheaper option could save about $1,000, the speaker preferred to buy suitable equipment and focus on earning the cost back.

Metrics, Targets, and Timelines

• Byte Me’s revenue for the month discussed: €10,000, or approximately $11,000.
• Historical monthly operating cost: about €3,000 for two full-time people. The speaker noted that compensation had already been kept very low.
• Example asset purchase: $40. Waiting for a sale might save around $20 but delay work by roughly two weeks—or potentially three weeks, as mentioned in the opening example.
• Thomas’s proposed laptop: approximately €4,400. The speaker says the company could recover 21% tax in Belgium.
• Studio ambition: $1 million in studio revenue or value, described as becoming a million-dollar studio. The speaker predicts 2027 is likely to be the year Byte Me reaches “a milli,” though this is an aspiration or prediction, not a guarantee.
• Project durations cited: small games of 2–4 months and M198 at about 100 days.

Presenter and Sources

• Presenter: The unnamed founder or representative of Bite Me Games.
• Sources and examples cited: A discussion in the Bite Me Discord involving a member referred to as Groth/Grod in the subtitles; Byte Me’s experience with Desktop Island, Silicon Architect, and M198; and team members William and Thomas.