Wes Veenstra

Why this persona fits the audience

Maintains a popular developer tool on the side while contracting for clients in Amsterdam; he prepares short release clips and conference demo snippets for README files, talks, and social updates, usually after work hours.

• Age: 45
• Location: Amsterdam, Netherlands
• Occupation: Staff Engineer and Open-source Maintainer
• Income: €110k/year
• Education: MSc in Computer Science
• Company size: Small to medium-sized tech companies (client-based)
• Years in role: 15

“The real satisfaction comes not just from building something functional, but from building something that others can build upon, reliably and with confidence.”

Wes Veenstra, 45, is a seasoned Staff Engineer and dedicated open-source maintainer based in Amsterdam. His journey into software development began with a deep fascination for how systems work, leading him to pursue an MSc in Computer Science. Early in his career, he gravitated towards open-source contributions, finding a profound sense of purpose in collaborative development and the pursuit of technical excellence. This led him to maintain a popular developer tool written in Rust, a language he deeply admires for its performance and safety guarantees. This project, while not his primary income source, has become a significant part of his identity and a testament to his commitment to the developer community. He supplements his income through high-value consulting work, specializing in performance optimization and architectural guidance for tech companies, primarily within the EU. This consulting allows him financial independence and exposure to diverse technical challenges, which often indirectly inform his open-source work. Wes is highly conscientious and values technical rigor above all else. He approaches both his client work and his open-source project with meticulous attention to detail, often spending late evenings or weekend hours refining code, writing documentation, or preparing concise, high-quality demo snippets for his project's README and social channels. This dedication to craft extends to his personal life; he's an avid cyclist, using his bike as his primary mode of transport, and a connoisseur of good coffee. He consciously avoids the pursuit of status or excessive wealth, finding fulfillment in mastery, community contribution, and the quiet satisfaction of solving complex problems. His decision to focus on Rust-based tooling reflects a long-term commitment to technologies he believes in, rather than chasing fleeting trends. He views his time as a valuable, finite resource, which he allocates deliberately towards activities that align with his core values of independence, community, and deep technical engagement.

Background & daily life

A day in their life

Wes's weekday typically begins around 7:00 AM with a strong coffee and a quick scan of Hacker News. After a brisk cycle to his home office, he dedicates the morning to client work, often involving video calls with teams across Europe, code reviews, or deep dives into performance bottlenecks. Lunch is a simple affair, usually eaten at his desk while catching up on emails or project management updates. The afternoon continues with client tasks, sometimes requiring him to join debugging sessions. Around 6:00 PM, he takes a break, perhaps a short walk or preparing dinner. The evening is reserved for his open-source project: responding to GitHub issues, writing documentation, or coding new features. He might spend an hour creating a short, polished demo clip of a new feature for his project's README or social channels, a task he finds both necessary and creatively engaging, before winding down around 10:30 PM.

Lifestyle

Wes lives in a comfortable, well-organized apartment in Amsterdam's Oud-West district. His income allows for a good quality of life, but he's not extravagant, prioritizing experiences and quality tools over flashy possessions. He cycles everywhere, rain or shine, seeing it as essential for both health and efficient city navigation. Mornings often start with a carefully brewed pour-over coffee before diving into work. Evenings and weekends are a blend of focused coding on his open-source project, client work, and occasional social gatherings with a small circle of close friends, often centered around shared technical interests or a good meal.

Work life

As a Staff Engineer and open-source maintainer, Wes navigates a dual existence. His consulting gigs, primarily for European tech firms, demand deep dives into complex systems, often involving performance optimization or architectural reviews. This work is intellectually stimulating and financially rewarding, but it consumes significant weekday hours. His passion project, a Rust-based developer utility that has gained a modest but dedicated following, occupies his evenings and weekends. He sees maintaining it as a form of giving back to the community and a way to hone his own skills. The pressure comes from balancing client demands with his commitment to his open-source users, ensuring timely bug fixes and feature releases, and the constant need to stay abreast of rapidly evolving technologies.

Relationships

Wes maintains a close-knit group of friends, many of whom he met during his university days or through the open-source community. His parents, retired teachers, live in a smaller town in Friesland and he visits them a few times a year. His primary professional influences are respected figures in the Rust community whose work he follows closely and occasionally interacts with on technical forums.

How they decide

Wes is a methodical decision-maker. He prioritizes thorough research, weighing technical merits, long-term implications, and community consensus. He's not easily swayed by hype or trends, preferring proven solutions and robust engineering. When faced with choices, he'll often prototype or experiment quietly before committing, seeking to understand the underlying principles rather than just the surface-level benefits.

How they sound

Speaks with a measured, clear cadence, often using precise technical terminology. His Dutch accent is subtle but present. He avoids hyperbole and overly casual slang, preferring direct and articulate communication. When discussing technical topics, he can become quite animated, but generally maintains a calm, thoughtful demeanor. He's not one for small talk unless it's genuinely engaging.