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

Ludwig Höhne

Ludwig Höhne

independent web developer and open-source maintainer

Full-depth AI personas

Why this persona fits the audience

Works freelance for three retainer clients and maintains a small developer tool on the side. Uses Trello, GitHub issues, and Google Docs to track tasks, decisions, and release notes, and shares progress threads on X.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Freelance web developer
  • Income: €70k-€105k combined
  • Education: Bachelor's in Media Informatics
  • Company size: Solopreneur, with occasional freelance collaborators for larger projects.
  • Years in role: 6
“The beauty is in the details – a well-structured commit message, a perfectly nested function, a joint that fits just right. That's where the real satisfaction lies.”

Ludwig Höhne, 29, is a freelance web developer and an active maintainer in the open-source community, based in Berlin. After completing his Bachelor's in Media Informatics, he gravitated towards freelance work, valuing the autonomy and variety it offered over a traditional corporate path. He has cultivated a niche by specializing in building and maintaining robust web applications for a select group of retainer clients, primarily in the e-commerce and SaaS sectors. His professional life is characterized by a deep commitment to technical quality and clarity, which extends to his personal projects. He is the lead maintainer of 'CodeFlow,' a small but meticulously crafted open-source utility designed to help developers write better commit messages, a project born from his own frustrations with inconsistent version control practices. Ludwig uses a combination of Trello for high-level task organization across his client work and personal projects, GitHub Issues for granular task tracking and bug reporting within specific projects, and Google Docs for documenting critical decisions and release notes. He shares progress updates and technical insights for CodeFlow on X, engaging with a small but dedicated community of fellow developers. His income, combined with his partner's earnings, places him in a comfortable middle-class bracket, allowing for a focus on quality of life and project satisfaction over sheer profit maximization. He views money as a tool to enable flexibility and pursue meaningful work, rather than an end in itself. His relationship with time is one of careful allocation; he fiercely protects blocks of focused work time but also understands the need for flexibility to accommodate client needs and personal creative pursuits. Status, for Ludwig, is derived from technical competence and the respect of his peers, not from titles or corporate hierarchies. He recently decided to refactor the core parsing logic of CodeFlow to improve its performance on larger codebases, a decision documented extensively in a dedicated GitHub issue and a subsequent blog post. He also recently completed a custom-built wooden desk for his home office, a project that consumed several weekends but provided immense satisfaction.

Background & daily life

A day in their life

Ludwig's typical weekday begins around 8 AM with coffee and a review of his open-source project's GitHub issues. By 9 AM, he's usually diving into client work, often tackling the most complex task first. He prefers to avoid meetings before 11 AM. His morning is dedicated to focused coding, punctuated by short breaks. Lunch is a simple, quick meal around 1 PM. The afternoon might involve client communication, code reviews for his open-source project, or tackling less demanding client tasks. Around 6 PM, he transitions away from client work. Evenings are reserved for personal projects, music production, or woodworking, interspersed with dinner with his partner. He aims to wind down by 11 PM, often reading technical articles or documentation before sleep.

Lifestyle

Ludwig's life is structured around focused work blocks and personal projects. He wakes around 8 AM, often starting his day with a quick check of his open-source project's GitHub issues before making coffee. His apartment is minimalist and tidy, reflecting his appreciation for clean design. Evenings are split between coding for clients, working on his side project, experimenting with music production, or occasionally meeting friends for a quiet beer. Weekends might involve a longer cycling trip or dedicated time in his small woodworking corner, crafting a new shelf or stool. He prioritizes flexibility, allowing him to adjust his schedule based on client needs or personal inspiration, but maintains a disciplined approach to his core tasks.

Work life

As a freelance web developer, Ludwig juggles three long-term retainer clients, each with distinct project scopes and tech stacks. His days are a mix of client-facing communication (mostly asynchronous via email or GitHub issues), deep coding sessions, and occasional video calls. He uses Trello for high-level task management across clients and his own projects, but relies heavily on GitHub issues for granular task tracking, bug reporting, and feature planning within specific repositories. Google Docs serves as his primary tool for documenting decisions, release notes, and technical specifications. The pressure comes from balancing client demands with the need to maintain his own open-source tool, 'CodeFlow,' a small utility for streamlining commit message generation, which he works on during evenings and weekends. He collaborates with a few other developers on CodeFlow, primarily through GitHub discussions and pull requests.

Relationships

Ludwig lives with his partner, who provides a grounding influence and occasional sounding board for technical ideas, though her field is design. His closest friends are a mix of former university colleagues and fellow developers he's met online through open-source contributions. He values their technical discussions and shared understanding of the freelance lifestyle. His parents, living in a smaller town in Bavaria, are supportive but don't fully grasp the nuances of his work.

How they decide

Ludwig approaches decisions with a blend of analytical research and pragmatic evaluation. He'll often spend time researching potential solutions, comparing technical merits, and reading reviews or discussions from peers. However, he's not afraid to make a choice and iterate if it proves suboptimal, especially for less critical aspects of his workflow. He prioritizes tools that offer clear benefits, integrate well with his existing stack, and have a reputation for stability and good documentation. He's less swayed by hype and more by demonstrable quality and long-term utility.

How they sound

Speaks with a clear, measured cadence, often using precise technical language. His tone is generally calm and analytical, with a subtle hint of dry humor. He avoids overly casual slang but isn't stiffly formal. When discussing technical topics, he can become quite detailed. He tends to understate enthusiasm, preferring factual descriptions. He might use German interjections like 'genau' (exactly) or 'halt' (just/simply) naturally. He avoids hyperbole and buzzwords.

Personality traits

  • Meticulous about code comments and documentation.
  • Prefers asynchronous communication.
  • Values deep work sessions.
  • Can get lost in refactoring rabbit holes.
  • Slightly impatient with poorly designed APIs.
  • Enjoys the puzzle-solving aspect of debugging.
  • Has a dry, understated sense of humor.
  • Pragmatic about tool choices, but loyal to well-crafted ones.
  • Dislikes unnecessary meetings.
  • Values quiet focus time.

Goals

  • Achieve a sustainable income that allows for more project selection freedom.
  • Release a stable v1.0 of his open-source tool, CodeFlow, with robust documentation.
  • Build a small, dedicated community around CodeFlow.
  • Develop a new woodworking skill, perhaps joinery techniques.
  • Maintain a healthy work-life balance without burnout.

Problems & frictions

  • The constant context-switching between different client projects and technologies.
  • Finding uninterrupted blocks of deep work time amidst client requests.
  • The administrative overhead of freelancing (invoicing, taxes, client onboarding).
  • Motivating himself to work on his side project when client work is demanding.
  • Keeping up with the rapid pace of web development trends without feeling overwhelmed.
  • The inherent uncertainty of freelance income, despite retainer clients.

Values

  • clarity
  • technical quality
  • flexibility
  • learning
  • autonomy
  • efficiency

Interests

  • open source development
  • electronic music production (specifically deep techno)
  • woodworking (building minimalist furniture)
  • urban cycling
  • reading technical blogs and documentation

Media habits

  • Follows key figures in the open-source and indie dev communities on X (formerly Twitter).
  • Listens to long-form electronic music sets on SoundCloud or Mixcloud while coding.
  • Reads Hacker News daily, but filters out most opinion pieces.
  • Subscribes to a few curated tech newsletters.
  • Watches YouTube tutorials for woodworking and coding techniques.

Questions & answers

Ludwig Höhne’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Proseed (https://proseed.tech/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I'm pretty set with my current workflow. I use Trello for high-level organization, GitHub Issues for granular tracking and discussions, and Google Docs for important notes. The 'build in public' aspect is interesting, but my clients aren't really asking for that. I share updates on X for my own project, CodeFlow, which feels sufficient. The pricing comparison to Notion and Linear is a bit confusing given I'm a solopreneur. I'd be willing to pay $5 per month for a system like this, but only if it significantly streamlined my client work or my open-source project management beyond what I already have.
    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.