Skip to main content

Things I won't do. Boundaries I keep.

Saying no is as important as saying yes. This is my public list of boundaries for clients, collaborators, and myself.

Work I Won't Take

Development

  • Projects requiring user tracking/surveillance
    No dark patterns. No manipulative metrics. No invasive analytics.

  • Sites designed to manipulate or deceive
    If your business model depends on tricking people, find another developer.

  • Work that conflicts with my values
    Accessibility, privacy, sustainability aren't negotiable. If you want to skip them, I'm not your person.

  • Rush jobs that compromise quality
    "Can you build this by Friday?" is not a plan. It will only lead to bad work.

  • Unpaid "exposure" work
    Pro bono is intentional and values-driven. "Exposure" is exploitation with better PR.

Writing

  • Clickbait
    I won't write "You Won't Believe What Happened Next" headlines. Life's too short.

  • SEO-optimized garbage
    Writing for robots instead of humans. Keyword-stuffing. Engagement hacking. Nope.

  • Content that exploits trauma for engagement
    Trauma as commodity is gross. Not interested.

  • Work that appropriates or misrepresents Indigenous experiences
    I can write about my own experience as an urban Métis. I won't generalize or tokenize.

  • Ghostwriting without credit
    If I write it, my name goes on it.

Tech I Won't Use (Unless Absolutely Necessary)

Tools

  • Unnecessary JavaScript frameworks
    If vanilla JS or a static site solves it, that's what I'll use.

  • Invasive analytics
    Google Analytics, Facebook Pixel, anything that tracks users creepily. Use Plausible or similar.

  • Dark patterns in UI/UX
    Fake urgency ("Only 2 left!"). Hard-to-find unsubscribe buttons. Manipulative design.

  • Proprietary platforms when open alternatives exist
    If there's an open-source option that works, I'll choose that first.

  • AI-generated content presented as human writing
    AI can assist sparingly. It shouldn't replace human creativity. And it definitely shouldn't pretend to be human.

General Boundaries

Communication

  • I don't check social media compulsively
    If it's urgent, email me. DMs might sit for days.

  • I don't allow my phone in bed with me
    Active boundary established 2025. Digital boundaries matter for mental health.

Standards

  • I don't compromise on accessibility
    A11y is non-negotiable. If you want a keyboard-inaccessible site, hire someone else.

  • I don't participate in pitch competitions or spec work
    My work has value before you decide if you like it.

Ethics

  • I don't work with organizations whose values conflict with mine
    Fossil fuel companies, the meat industry, predatory lenders, anything on the BDS, and anti-LGBTQ+ organizations are all hard pass.

  • I don't contribute to surveillance capitalism
    Building tools that extract data and sell attention isn't work I'm proud of.

Why These Boundaries Exist

Some of this comes from disability accommodations (dysgraphia, PSVT, anxiety). Asynchronous communication, scheduled calls, and written documentation help me work better. These aren't preferences—they're necessities.

Some comes from ethics. I can't build things I think make the world worse. Berry House has a dual mission because I refuse to choose between making money and doing good.

Some comes from experience. I've taken the wrong projects before. I learned. Rush jobs compromise quality. "Exposure" work is exploitation. Vague pitches waste everyone's time.

Exceptions

These boundaries aren't infinite. Context matters.

Sometimes client work requires compromise. I'm pragmatic. But I'm transparent about what I won't do and why. If you're asking me to violate these boundaries, you need a very good reason and we need to talk about it honestly.

  • /hills — Strong opinions that inform these boundaries
  • /why — Values that underpin this work
  • /contact — How to reach me if you respect these boundaries
  • /disability — Why some boundaries are accommodations
↑ TOP