Designing for the Oregon Coast: What Remote Work Actually Looks Like

I build web applications from Newport, Oregon, a fishing town of about 10,000 people on the central coast. The nearest city with a co-working space is Corvallis, an hour and a half inland. My office is a room that smells like salt air and sounds like the neighbor's boat engine starting at 5am.

Most people who hear this assume it's romantic. It is, and it also comes with real constraints that shape how I work.

The Reliability Problem

Internet on the Oregon coast is unreliable by urban standards. I run a Starlink dish because fiber stops about two miles east of my house. On stormy days — which is most of winter — I've learned to save frequently, commit often, and avoid live demos during Zoom calls unless conditions are calm.

This shaped my habit of building async-first. Client communication is primarily written. When video calls happen, I record them. I over-document decisions because I've learned that "I'll remember that" is a lie when you're living in an environment that makes you want to go check the surf report instead.

What the Coast Does to Your Eye

Spending time outdoors in a visually dramatic environment recalibrates what you consider "enough contrast" and "enough whitespace."

The Oregon coast has no gentle gradients. It's gray water, black basalt, white surf, and dark green Sitka spruce. Everything is high contrast, textured, and in motion. Spending enough time in that environment makes you intolerant of the low-contrast, visually homogenous gray card grids that dominate SaaS design.

I don't know exactly how this shapes my design decisions, but I know that my first instinct on any layout is always to push contrast further and reduce clutter more aggressively than the initial draft warrants.

The Depth of Presence Problem

Remote work from a physically engaging environment creates a specific attention management challenge: the ocean is always there. On a good swell day, it's very hard to write TypeScript.

My solution is schedule-based deep work: 6–10am is code time, no exceptions. After that, attention is available for meetings, reviews, and the beach. The schedule protects the work without making the location pointless.

Why It Works for This Kind of Work

Client work in web development doesn't require geographic proximity to clients. Every deliverable is digital. Every collaboration tool exists online. And there's a strong argument that novel physical environments produce more creative problem-solving than office parks.

The thing I did not expect: local clients. Newport has a growing number of small businesses that are actively underserved by the digital tools available to them. Fishing companies, tour operators, small restaurants, and local retailers who need real web presence — not a Facebook page — and don't know where to start. Some of my most satisfying projects have come from walking distance.

The Real Answer

People ask whether it's sustainable to run a web development practice from a small coastal town. The answer is yes, with the usual caveats: you need strong client relationships, you need to be excellent at async communication, and you need to be honest about what "remote" means for your particular kind of work.

For shipping code? Highly compatible. For in-person discovery workshops with enterprise clients? Less so.

I've found my equilibrium, and it involves a lot of rain, strong coffee, and a standing desk positioned so I can see the ocean without being able to see when the surf is good.