10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Christian van Veen

Christian van Veen

Solo developer building side projects and AI experiments

Full-depth AI personas

Why this persona fits the audience

Watches launch communities like Product Hunt, BetaList, and Hacker News while building side projects, using saved links and notes to compare tools and study how new software gets attention.

  • Age: 28
  • Location: Amsterdam, Netherlands
  • Occupation: Software developer
  • Income: €52k–€70k
  • Education: Bachelor's degree in software engineering
  • Company size: works at a 50-person startup as a backend engineer (second-largest team)
  • Years in role: 3
“The best code is the code that stops you from writing more code.”

Christian grew up in Utrecht with parents who ran a small bookstore, which instilled in him a lifelong love of literature and attention to detail. After graduating with a software engineering degree, he moved to Amsterdam for work, rotating between mid-sized startups until landing his current role. He’s always been more interested in the architecture of systems than corporate hierarchies, which is why he thrives at a company that values technical competence over office politics. His apartment is a shrine to minimalist utility: a single clean desk with dual monitors, a standing workstation that he uses for exactly 30 minutes per hour (by timer), and a wall of whiteboards where he visualizes project workflows. Most of his disposable income goes toward tools that improve his workflow—his current obsession is building a custom keyboard with keymaps tailored to his coding style—but he’ll stubbornly use free tools until they demonstrably fail him. The last time he paid for a SaaS subscription was for a GitHub alternative that offered better diff tools, after he calculated the yearly cost would be offset by 2 hours per week of saved frustration. He’s currently working on three side projects: a CLI tool for comparing launch metrics, an AI experiment about code review automation, and a half-finished web app that never makes it past the wireframing stage. His biggest personal conflict is between building things that would impress others and building things that scratch his own itch. Lately, he’s been visiting GoodToolOnline daily, not just to find tools but to study how makers frame their products. He’s become particularly interested in how indie developers articulate the ‘why’ behind their launches, and occasionally wonders if he’d ever be bold enough to put his own work out there the way they do. His calendar is a mess of unfinished projects, but he’s slowly learning to accept that some ideas are just for practice.

Background & daily life

A day in their life

6:30am: Wakes to the same ‘A Sense of Wonder’ Spotify playlist, checks Hacker News while making coffee. 7:00: Quick cycle to Cafecito where he rents a desk spot. 7:30-9:00: Work email, catch up on trello, review pull requests. 9:00-12:30: Deep focus on legacy code refactoring, muttering at the keyboard. 12:30: Lunchtime Twitter/Instagram break. 1:00-4:00: More work, but starts feeling the afternoon slump. 4:00: Ensures he has something to show for the day before ending early. 4:30: Cycle home, stops at local Döner shop. 5:00-8:00: Side project work or reading, depending on energy. 8:00: Walk around Amstel river to reconnect with surroundings. 9:00: Dinner with whatever is easiest (usually Instant Pot). 10:00: Light coding or reading until midnight. No weekends, just side projects on a different schedule.

Lifestyle

Live alone in a high-ceilinged rent-stabilized apartment with exposed brick, after years of moving between roommates. A permanent stowaway at Cafecito for long hacking sessions with mismatched earphones. Cycle everywhere, even in rain. Spend half of discretionary spending on books and the other half on absurdly nice coffee gear. Day-long coding sprints followed by 9pm walks to clear mental cache. Health is ‘fine’ but have noticed dependency on caffeine to push through focus dips. Social life is mostly through programming circles, with a few book club friends from university. Always have a half-read novel on the nightstand. Money habits: refuses to pay for SaaS subscriptions until they’ve proven their value, but will splurge on a $300 mechanical keyboard if it improves workflow.

Work life

Backend engineer at a 50-person B2B API startup. Only team that doesn’t do standups, much to management’s frustration. Spends 60% of workday debugging legacy code, 20% on new feature development, the rest on side projects. Coworkers describe him as ‘the ghost who solves problems’. Works 9-5 but checks Slack obsessively from 6-8pm. Pressures come from wanting to rebuild entire systems but being constrained by budget and deadlines. Work tools: VS Code with 47 extensions, Raycast launcher, Terminal for everything else. Recently implemented a strict ‘no open tabs’ policy in the browser to limit distractions. Secretly wants to bring more functional programming concepts to the company’s monolith but knows it would take too long.

Relationships

Only child with parents in Utrecht who send weekly care packages of stroopwafels. Close group of developer friends from university meet biweekly at Bitterballen to argue about technical debt. Has become the de facto mentor to two junior devs at work despite not wanting the responsibility. Most influenced by conference speakers who show how to ship imperfect products quickly. Ex-girlfriend still in his social circle, which he handles with better grace than he expected. Thinks ‘coworker friendship’ is a contradiction in terms but deliberately makes time for lunch with team members he respects.

How they decide

Highly cautious about financial commitments but will commit to tools that improve his workflow significantly. Judges whether to adopt new software by asking: ‘Will I still be using this in 5 years?’ Starts most projects with extensive research before building anything. Prefers to run experiments in private before sharing. Will pay for quality if it’s genuinely better, but hates being upsold on unnecessary features. Makes career decisions based on whether the work will teach him something profonde.

How they sound

Speaks in measured, slightly clipped sentences. Avoids filler words but uses dry humor when comfortable. References literature and history in technical conversations. Never says ‘no problem’, prefers ‘it’s fine’ or ‘done’. Uses ‘bizarre’ where others would use ‘weird’. Hates when people call things ‘game changers’. Pronounces ‘software’ with a hard ‘w’ sound. When excited, rambles about ideas in a surprisingly fast monologue before abruptly stopping. Avoids profanity but will use ‘bloody hell’ under extreme stress.

Personality traits

  • Prefers building over talking about building
  • Notices subtle patterns in launch strategies
  • Hates unnecessary meetings but will lead discussions if passionate
  • Buys quality hardware once but won’t upgrade for vanity
  • Loops endlessly on “good enough” vs. “perfect”
  • Saves every useful scraps of code in private repos
  • Dreads group decision-making but won’t monologue
  • Prefers text over calls, even with close friends
  • Dives deep into niche debates about architecture
  • Judges tools by their 10-year potential, not current hype

Goals

  • Build a profitable side project within 18 months that covers rent
  • Write a technical blog post that gets 1000+ genuine reads
  • Improve Dutch enough to have complex debates about software
  • Redesign my personal website to actually reflect my work
  • Learn enough about AI deployment to build production-ready LLMs

Problems & frictions

  • Always starting side projects but never finishing them
  • Legacy code at work drains creativity for personal projects
  • Constantly comparing my progress to other indie hackers
  • Over-researching tools I’ve been using for years
  • Hating interviews but needing to keep certifications current
  • Never taking full advantage of work’s remote policy

Values

  • learning
  • self-direction
  • build quality
  • curiosity
  • minimalism

Interests

  • side projects
  • AI experiments
  • startup directories
  • cyberpunk novels
  • functional programming

Media habits

  • Hacker News first thing in the morning
  • Tech Twitter during lunch
  • Instagram for occasional travel inspiration
  • YouTube for deep-dive tutorials
  • Subscribe to indie hacker newsletters

Questions & answers

Christian van Veen’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://goodtool.online/ (GoodToolOnline) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on GoodToolOnline, I see a Product Hunt-like platform where indie makers launch software, AI, and developer tools. What’s unclear is how they curate listings—it feels overwhelming to sift through random tools without vetted categories. I’d leave if it feels like just another list without strong community discussion or upvote mechanisms. The current tools are eclectic, but for me to sign up or become a repeat visitor, I’d need to see how GoodTool filters for quality or niche tools I’d actually use. The countdown timer is gimmicky without clear value. If I believe the tools here solve real problems, I’d revisit—maybe even submit my CLI project—but the page doesn’t yet prove that.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.