Platon Kaczmarski

Why this persona fits the audience

Builds side projects with two friends in a 3-person team, using GitHub issues, spreadsheets, and a paid launch-list subscription to keep weekly releases organized. He handles the technical setup and the submission workflow.

• Age: 35
• Location: Kraków, Poland
• Occupation: Software engineer and indie hacker
• Income: 220k PLN/year
• Education: MSc in computer science
• Company size: Works remotely for a medium-sized tech company (approx. 200 employees)
• Years in role: 10

“The elegance of a well-designed system isn't just in its function, but in how little friction it introduces.”

Born and raised in Poland, Platon Kaczmarski developed an early fascination with how things work, which naturally led him to computer science. After earning his MSc, he quickly established himself as a competent software engineer in the professional world, working for a medium-sized tech company where he contributes to complex backend systems. His innate drive for creation and problem-solving, however, couldn't be contained within a single role. Platon is also a dedicated indie hacker, a pursuit he shares with two close friends. Together, they form a tight-knit, three-person team that meticulously plans and executes weekly releases of their side projects. Platon's specific role involves the crucial technical setup, from infrastructure to CI/CD pipelines, and managing the entire submission workflow for their product launches. They currently organize their efforts using GitHub issues for task tracking, spreadsheets for managing metrics and user feedback, and a paid subscription to a launch-list service to ensure visibility for their new releases. This structured approach reflects his core values of competence, precision, and building momentum. His income of 220k PLN annually provides a comfortable life, allowing him and his partner to live well in Kraków while still enabling him to reinvest time and some resources into his entrepreneurial ventures. He sees his side projects not just as potential revenue streams, but as proving grounds for new ideas and a way to maintain his edge in a constantly evolving tech landscape. Recent decisions have focused on automating parts of their release process to reduce manual overhead, a direct response to the increasing complexity of their projects and the limited time available outside his primary employment. He is deeply invested in the open-source community, contributing when time permits, and views chess not just as a hobby but as a training ground for strategic thinking and pattern recognition, skills he directly applies to both his professional and indie hacking endeavors.

Background & daily life

A day in their life

Platon's weekday typically begins around 6:00 AM. He makes coffee and dedicates two focused hours to his indie hacking projects, often tackling complex coding tasks or refining deployment scripts. After a quick breakfast, he logs into his full-time engineering job, where his day involves team meetings, writing and reviewing code, and architectural discussions. Lunch is usually a pre-prepared meal eaten at his desk while scanning Hacker News. The afternoon might involve deep-dive debugging or collaborating on feature development. By 5:00 PM, he logs off from his job, takes a short break, and then might spend another hour or two on his side projects, possibly coordinating with his co-founders via Slack or GitHub issues, before dinner and winding down with his partner.

Lifestyle

Platon shares a modern apartment in Kraków with his partner, who works in marketing. His evenings and weekends are a careful balance between his full-time job, their shared life, and the ambitious indie hacking projects. He's disciplined about his routine, often waking early to get a few hours of focused work on his side projects before his day job begins. While he enjoys the occasional social gathering, he generally prefers quiet evenings at home. Financial discipline is key; he tracks expenses meticulously and views savings as a direct path to future autonomy and project funding. He prioritizes efficiency, whether it's in his code or his meal prep.

Work life

As a senior software engineer, Platon's days are filled with complex problem-solving, code reviews, and collaborating with his distributed team. The pressure to deliver robust solutions on time is constant, but he thrives on the challenge. His role involves architecting new features and ensuring the scalability of existing systems. For his side projects, the dynamic is entirely different: it's about rapid iteration, direct user feedback, and the satisfaction of building something tangible from scratch with his co-founders. Managing releases, ensuring smooth deployments, and keeping the project roadmap aligned with his friends are his primary concerns.

Relationships

Platon's closest professional relationships are with his two indie hacking co-founders, with whom he shares a deep understanding and a collaborative spirit built over years of working together. He also maintains cordial working relationships with his colleagues at his main employer, though he keeps his side projects private. His partner is his primary confidante, offering emotional support and a grounding perspective on his ambitious pursuits.

How they decide

Platon is a highly analytical and research-driven decision-maker. He meticulously gathers information, compares alternatives based on objective criteria, and often seeks out case studies or benchmarks before committing. He values precision and avoids impulsive choices, preferring to ensure a decision aligns with long-term goals and efficiency. Peer recommendations are considered, but only after he's done his own due diligence.

How they sound

Speaks with a measured, precise cadence, using clear and technically accurate language. He avoids hyperbole and excessive slang, preferring straightforward communication. His tone is generally calm and objective, even when discussing challenges. He often uses analogies from programming or system design to explain concepts. He is unlikely to use overly emotional language or make sweeping generalizations.