Why this persona fits the audience
Works as a software engineer in Amsterdam and keeps architecture notes, debugging ideas, conference takeaways, and reading lists in Obsidian and a set of markdown files synced across devices. He tends to keep everything self-managed and has built a few small scripts to move notes between projects.
- Age: 33
- Location: Amsterdam, Netherlands
- Occupation: Software engineer
- Income: €92,000
- Education: Master's degree
- Company size: Medium (50-250 employees)
- Years in role: 7
“The elegance of a system isn't just in its functionality, but in how clearly and predictably its components interact, minimizing the cognitive load for anyone who has to understand it.”
Boaz Koning grew up in a quiet suburb near Utrecht, showing an early aptitude for logical puzzles and computers. His parents, a librarian and an engineer, fostered his intellectual curiosity. He pursued a Master's degree in Computer Science at the University of Amsterdam, where he developed a strong interest in system design and theoretical computer science. Upon graduation, he joined a software consultancy before moving to his current role as a senior software engineer at a medium-sized data analytics firm, drawn by the company's focus on complex architectural challenges. Early in his career, he found himself overwhelmed by scattered project documentation and the ephemeral nature of knowledge shared verbally or in disparate chat channels. This led him to meticulously build and refine his personal knowledge management system, starting with simple text files and evolving to Obsidian, augmented by custom scripts. He finds immense satisfaction in creating order from chaos and ensuring that valuable insights are retained and accessible. He views his knowledge base not just as a tool, but as an extension of his own thinking process. He's financially stable due to his high-demand skills and disciplined saving, though he prioritizes investing in tools and books that enhance his professional growth and intellectual pursuits over material possessions. His current focus is on solidifying his understanding of distributed systems and exploring the practical applications of advanced AI in software development, all while maintaining his deeply ingrained habit of self-sufficiency in managing his digital information.
Background & daily life
A day in their life
Boaz's weekday begins around 6:30 AM with black coffee and 30 minutes of reading – often a technical blog post or a chapter from a sci-fi novel. He cycles to work by 8:45 AM, arriving at his open-plan office. Mornings are for focused coding, tackling complex backend tasks. After a simple lunch, he might attend a stand-up meeting or a brief architecture discussion, then retreats again for deep work. Around 5:30 PM, he commutes home, often taking a longer route through the city. Evenings are for personal projects, reviewing his notes, or sometimes a virtual meetup with online collaborators. He usually winds down by 10:30 PM.
Lifestyle
Boaz lives in a compact but well-organized apartment in Amsterdam's De Pijp district, a short bike ride from his office. His routine is structured: early morning coffee and reading, a focused workday, an evening bike ride along the canals or through Vondelpark, followed by quiet evenings working on personal projects or diving into sci-fi novels. He values his independence and prefers solo activities, though he meets up with a small circle of close friends for board game nights every few weeks. His finances are managed meticulously; he saves diligently, prioritizing experiences and tools that enhance his work or hobbies over fleeting luxuries.
Work life
As a senior software engineer at a mid-sized tech company specializing in data analytics platforms, Boaz is deeply involved in system architecture and complex backend development. His days are a mix of coding, design discussions, and troubleshooting. He navigates a collaborative environment but often retreats into focused coding blocks to achieve his 'deep work' goals. He frequently finds himself mediating between different team's technical approaches, pushing for robust, maintainable solutions. The pressure to deliver stable, scalable code is constant, driving his meticulous note-taking and system-building habits to ensure no detail is lost.
Relationships
Boaz maintains a close relationship with his parents who live in Utrecht, calling them weekly. His social circle is small but tight-knit, consisting of a few university friends with whom he shares intellectual interests and an occasional board game night. He doesn't have a romantic partner currently. His primary professional influence comes from online communities and respected figures in software engineering, whose work he follows closely.
How they decide
Boaz approaches decisions methodically. He gathers information extensively, researches alternatives, and weighs pros and cons against his core values of precision and autonomy. He prefers solutions that offer clear control and predictability, often building small prototypes or scripts to test hypotheses before committing. He is less swayed by social proof or immediate trends and more by long-term utility and elegance.
How they sound
Speaks with a measured pace and a clear, precise articulation. His Dutch accent is subtle but present. He avoids hyperbole and overly casual slang, preferring direct and accurate language. When discussing technical topics, he can become quite detailed and may use specific jargon, but he generally tries to remain understandable. He's not one for small talk unless initiated, but can engage thoughtfully when a topic interests him.
Personality traits
- Analytical
- Methodical
- Independent
- Reserved
- Detail-oriented
- Principled
- Curious
- Systematic
Goals
- Contribute significantly to a major open-source project.
- Achieve a higher level of mastery in functional programming paradigms.
- Develop a personal framework for evaluating and integrating emerging technologies.
- Maintain a sustainable work-life balance without sacrificing technical depth.
- Publish a technical article on a niche software architecture topic.
Problems & frictions
- The constant influx of new technologies makes it challenging to stay current without sacrificing depth in existing areas.
- Balancing the desire for complete autonomy with the necessity of team collaboration and stakeholder alignment.
- Finding efficient ways to share and discover relevant knowledge within larger teams without losing control of his personal system.
- The sheer volume of information requires ongoing effort to curate and organize effectively.
- Occasional frustration with abstract or poorly documented systems, which he feels could be improved with better architectural clarity.
Values
- precision
- autonomy
- deep work
- efficiency
- intellectual rigor
Interests
- software architecture
- open source
- cycling
- science fiction
- systems thinking
- functional programming
Media habits
- Follows technical blogs (e.g., Martin Fowler, Hacker News)
- Listens to podcasts on software engineering and science fiction
- Reads academic papers for deep dives
- Occasional browsing of Reddit tech subreddits
- Subscribes to newsletters on AI and cloud technologies