I spent 15 years being good at systems. I just didn't know why — or what it was costing me.

I'm Amanda Nelson — the Pythoness Programmer. Senior Full Stack Software Engineer, late-identified neurodivergent, chronic illness navigator. I built the reflection skills I now teach in the hardest stretch of my life so far.

Here's the version of my story that matters for why you're here.

Amanda Nelson - The Pythoness Programmer

How I Got Here

Before code, I spent 15+ years in communications, customer service, and systems building — pattern recognition and detail orientation without the neurodivergent label yet.

In 2020 I enrolled in a pandemic-era bootcamp; by 2021 I was at Zappos.com with a new ADHD diagnosis, fibromyalgia and chronic migraines already in the picture, and a body that had been asking me to slow down for years. I was laid off in January 2023 — clarifying, painful, and the push into building Pythoness Programmer.

What helped wasn't another productivity system. It was community — late-identified neurodivergent adults naming patterns I'd blamed on myself, and voices explaining how tech and productivity systems were built for one kind of brain while everyone else was expected to adapt.

I'm near Richmond, Virginia. Watching confederate statues come down in 2020 and the BLM reckoning cracked open decolonization for me — looking honestly at inherited systems and stopping blaming myself for struggling inside them. That changed how I think about my tools. That's where the Pythoness Programmer comes from: reflection skills built in the hardest stretch, kept on purpose after I got through it.

How I Work

I philosophize with other decolonizing neurodivergents about what tech friction reveals — what you have internalized and what your brain actually needs.

Together we ask: What is this struggle trying to teach you?

  • Reflect on patterns you keep repeating — and why they keep failing
  • Uncover what you absorbed from ableist, productivity-obsessed tech culture
  • Discover tools and frameworks that fit your brain
  • Build understanding so you don't make it a third time

I share that work through free guides, Lab Notes, and Pythoness Perspective — technical context, pattern recognition, and neurodivergent-centered reflection.

What's in a Name

Pythoness comes from the Pythia — the high priestess of Apollo at Delphi, the oracle at the Temple of Apollo. English later called her the Pythoness. She sat at a crossroads where people brought hard decisions. The work was demystifying complexity, not giving orders.

I keep the colonized English form on purpose. Apollo's temple sat on ground that once belonged to an older earth-and-serpent cult; names get overwritten, and pretending inherited systems are neutral is its own kind of erasure. That nod runs through my decolonization work — looking honestly at what we absorbed, and what was never built for us.

The Programmer half is the craft: software engineering, and a habit of reading the messy underside of big tech — the incentives, defaults, and infrastructure most product stories skip. Oracle-like pattern recognition meets code. Clarity for brains the stack was never designed for.

My Core Values

Learning

Digital fluency, not dependency — your aha moments, not reliance on mine.

Resourcefulness

Hidden-gem tools and approaches mainstream advice skips.

Serenity

Calm guidance — no pressure, judgment, or false urgency.

Inclusion

Affirming space for LGBTQIA+ folks, sex workers, and anyone marginalized by mainstream tech culture.

Humor

Levity at systems that were never built for us — part of the work.

Resilience

Understanding that makes the next hurdle survivable — capacity, not just a patch.

You're looking for a guide who helps you understand your tech struggles, not just patch them.

Who This Is For

  • A neurodivergent creative who keeps hitting the same workflow walls
  • Someone newly diagnosed (or still figuring it out) revisiting old patterns
  • A small business owner tired of tech that does not fit how you think
  • Someone who has tried every productivity tool and wonders if the tools are the problem

Who This Isn't For

  • People looking for emergency tech rescue
  • Anyone who wants you to "just fix it" without understanding why it broke
  • Folks who aren't interested in reflection or pattern work

Stay in the conversation

Read Lab Notes, browse free resources, or subscribe to Pythoness Perspective. If we have worked together before — or you have a specific case-by-case need — you can still reach out by email.

One-on-one sessions are not publicly offered right now. If you are a past client or have a specific case-by-case need, email me.