Profile

About

The full profile, rendered from the version-controlled source. Copy any section into LinkedIn.

Headline

Primary (default): Software Engineer | Open Source | Developer Tools | Systems

Alt A: Software Engineer: Developer Tools & Open Source

Alt B: Engineer building maintainable systems, developer tooling, and open source.

Guidance:

Primary headline leads with the title, then the three strongest differentiators.
Alt versions used when LinkedIn trims long headlines on mobile.
No emoji, no rocket ships. The work carries the enthusiasm.

Summary

Software engineer building maintainable systems, developer tools, and open source.

I spend most of my time where small engineering decisions compound: authentication, backend services, developer tooling, and Flutter. I write code the next engineer can understand, documentation that lives in the same commit as the code it describes, and reviews that are specific, technical, and kind.

I build in public and contribute to open source, because showing the work keeps the work honest.

Keywords: maintainable systems, developer tools, open source, authentication, backend, Flutter, architecture, documentation, code review.

About

Short (one sentence): Software engineer focused on maintainable systems, developer tooling, and open source.

Medium (three sentences): I'm a software engineer who cares about code that outlasts its authors. I work on maintainable systems, developer tools, and open source, with hands-on experience in authentication, backend services, and Flutter. I write about engineering, I review carefully, and I build in public.

Long (profile section): Software engineer focused on maintainable systems, developer tooling, and open source.

The longer I build software, the less I believe writing code is the difficult part. Keeping software understandable, maintainable, and adaptable is. That belief shows up in everything I make: clear interfaces, predictable structure, documentation written in the same commit as the code, and reviews that are concrete instead of ceremonial.

My work spans authentication systems, backend services, developer tools, and Flutter applications: the layers where small engineering decisions compound. I contribute to open source and I build my own tools in public, because the practice of showing the work keeps the work honest.

I believe the systems that last are the ones the next engineer can understand tomorrow, not just the ones that work today. If that's how you like to build, we'll get along.

Experience

Format: Most recent first. One project-focused bullet per role, one engineering-principle bullet per role.

Template per role:

Title: Company, Dates
First bullet: the biggest project, what it did, what it delivered.
Second bullet: an engineering decision or practice the role demonstrates (maintainability, docs, reviews, tooling).
Third bullet (optional): an outcome measured in real terms: fewer incidents, faster onboarding, a tool that removed a recurring task.

Guidance:

Write the bullets as facts, not adjectives. "Designed the auth service used by all 40k users" beats "responsible for authentication."
Every role should demonstrate at least one of the profile's themes: maintainable systems, developer tools, open source, communication.
Gaps are fine. LinkedIn doesn't need month-by-month coverage; it needs honest coverage.

Skills

Core (top of profile):

Maintainable systems & software architecture
Developer tools & CLI design
Open source contribution & maintenance
Code review & engineering communication
Documentation

Languages & frameworks:

Dart / Flutter
Backend services (REST, authentication)
Developer tooling (CLIs, build tooling)

Practices:

Test-driven thinking, tests as documentation
Continuous refactoring and small changes
Building in public

Guidance: Keep the top list short: three to six skills. Recruiters and hiring managers read the first line. Move skills you've actually used recently to the top; drop the rest.

Featured order

Featured Order

The featured section reads top-down. The first card sets the tone; the last card should round out the story.

Article: Building Software That Lasts. The thesis of the profile. Sets expectations for everything below.
Project: kit. A concrete, inspectable example of building in public. Shows the "developer tools" claim with an actual tool.
Best repository. Engineering in practice: authentication, Flutter, backend.
Open source contribution. Shows the practice, not just the claim.

Guidance:

Keep the first card an article: it's the most shareable and it states the philosophy.
Alternate formats (article, project, repo, contribution) so the section doesn't look like a list of the same thing.
Rotate the middle cards occasionally; keep #1 and the anchor card stable.

Interests

Maintainable software and software architecture
Developer tools and the craft of the command line
Open source, building in public
Reading code, debugging as a discipline
Flutter, authentication systems, backend services

Guidance: Follow people and topics that match these interests so the feed stays relevant and the profile reads as genuinely engaged. Engage honestly: likes and comments should add information, not just signal.

Open to work

Open to Work

Headline used with the banner: Open to software engineering roles: maintainable systems, developer tools, open source.

In the about section, if recruiting: "Open to roles where I can build maintainable systems, sharpen developer tools, and contribute to open source, with a team that treats code review and documentation as engineering."

Guidance:

Turn on the Open to Work badge only when actively looking; it reads as noise otherwise.
Name what you're looking for, not just that you're looking.
Keep it specific enough that the right person recognizes it, and the wrong person self-filters.

Banner Spec

Concept: Minimal white banner with a subtle engineering grid and Palmshed branding.

Elements:

White background. Nothing else competes with the profile photo.
A faint 12-column grid, just visible, suggesting structure without shouting.
A single green accent: the Palmshed mark or a thin rule at the bottom edge.
Short, centered tagline, set in Inter or IBM Plex Sans. Optional.

Dimensions:

LinkedIn banner: 1584 × 396 px (covers mobile + desktop).
Export at 2x (3168 × 792) for sharpness.

Tagline options:

"Software that outlasts its authors."
"Maintainable systems. Developer tools. Open source."

Text is secondary. The banner should read as a calm, structured surface: the same aesthetic as the rest of the profile.

See prompts/ for image prompts and assets/logos/ for the Palmshed mark.