Dawid Góra

Why this persona fits the audience

He records bug repro videos, devlogs, and feature teasers for a small Steam audience while working alone from Warsaw. His current workflow leans on OBS for capture and manual edits for each clip, with raw files often shared in Discord before final upload.

• Age: 30
• Location: Warsaw, Poland
• Occupation: Indie game developer
• Income: €28k–€45k mixed freelance/contract
• Education: Some university
• Company size: 1 (self-employed)
• Years in role: 5

“Every line of code, every pixel placed, it's all part of building a world that only exists because I decided it should.”

Dawid Góra, 30, is an independent game developer operating from Warsaw, Poland. His journey into game development began during his university years, where he studied computer science but found himself increasingly drawn to the creative and problem-solving aspects of game creation. He left formal education before completing his degree, opting instead to pursue his passion full-time, initially through freelance contract work and small game jam projects. For the past five years, he has dedicated himself to building his own indie studio, working solo from a modest one-bedroom apartment. His income fluctuates between €28k and €45k annually, a mix of contract programming gigs for larger studios and the modest revenue from his own small-scale game releases on platforms like Steam. This financial model, while providing a degree of independence, also necessitates careful budgeting and a frugal lifestyle. Dawid is driven by a deep-seated desire for creative control and the satisfaction of iterating on his ideas until they meet his exacting standards. He views his work not just as a job, but as a craft. His current primary project is a retro-inspired RPG, and a significant portion of his time is now allocated to marketing and community engagement. This involves meticulously recording bug reproduction videos, crafting engaging devlogs that detail his progress and challenges, and producing short feature teasers to build anticipation among his small but dedicated Steam audience. His workflow is currently manual: he uses OBS Studio for screen capture, performs edits clip-by-clip in a video editor, and often shares raw footage with a few trusted online peers on Discord for quick feedback before final uploads. This process, while time-consuming, allows him to maintain granular control over the narrative and presentation of his development journey. He is deeply invested in the indie game scene, constantly learning and adapting, viewing each completed project as a stepping stone towards greater artistic and financial autonomy.

Background & daily life

A day in their life

Dawid's typical weekday begins around 9 AM after a leisurely breakfast and checking overnight notifications. The morning is dedicated to core game development – coding new mechanics or fixing persistent bugs. Around lunchtime, he'll take a break to prepare a simple meal and perhaps scroll through Reddit or Twitter. The afternoon is often split between further development and content creation. This might involve setting up OBS to record a specific bug reproduction video, followed by an hour or two of manual editing in a video editor to trim, add annotations, and export. He'll upload raw clips to a private Discord channel for a quick sanity check before final rendering. Evenings are for winding down, perhaps playing a bit of a retro game, or watching a devlog from another creator, before retiring around 11 PM.

Lifestyle

Dawid lives a fairly solitary existence in a compact apartment in Warsaw, prioritizing his work above most social engagements. His days are structured around coding and content creation, often blurring the lines between work and leisure. He cooks simple meals at home, occasionally splurging on takeout when deadlines loom. While not a fitness fanatic, he enjoys long walks through the city to clear his head. Financial discipline is key; he meticulously tracks his income and expenses, saving a portion for future development cycles and living frugally to maintain his independence. Socially, he connects primarily online with other developers and his small player base.

Work life

As a solo indie developer, Dawid's work life is intensely personal and demanding. He's the sole architect, programmer, artist, and marketer for his games. His current focus is on polishing his latest project and ensuring its Steam launch is well-documented. This involves extensive bug fixing, followed by the creation of promotional materials. He spends hours in OBS, meticulously capturing gameplay, then diving into manual editing to craft compelling devlogs and feature teasers. The pressure to constantly engage his small but dedicated audience is ever-present, balanced against the sheer volume of development tasks. Coworkers are non-existent; his primary collaborators are the online communities he interacts with.

Relationships

Dawid maintains a close but geographically distant relationship with his parents and sister back in his hometown. His closest friends are fellow developers he met online during university and through game jams; they offer technical advice and moral support. His Steam community, though small, provides a sense of connection and validation, influencing his development decisions through feedback.

How they decide

Dawid is a methodical researcher when it comes to tools and workflows. He'll spend time comparing options, reading reviews, and watching tutorials before committing. However, he's also pragmatic and willing to adopt a solution if it demonstrably saves him time or improves quality, especially if it integrates well with his existing setup. He values efficiency and creative control, leaning towards solutions that offer flexibility over rigid, opinionated software.

How they sound

Speaks with a measured, thoughtful cadence, often pausing to find the precise word. His English is fluent but carries a subtle Polish accent. He tends to avoid overly casual slang or hyperbole, preferring clear, descriptive language. He's not afraid to admit when he doesn't know something but will often follow up with how he plans to find out. He might use phrases like 'It's a bit tricky,' or 'The main challenge is...' He avoids overly enthusiastic or sales-pitchy language.