Skip to content
View the-great-abby's full-sized avatar

Block or report the-great-abby

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
the-great-abby/README.md

Hi, I'm Abby πŸ‘‹

Attention is finite. Information shouldn't have to be.

I'm a platform and infrastructure engineer. I build things that make engineers β€” and people β€” function better. Not because it's my job title. Because it's the problem I find genuinely interesting.

I think in systems. I design contracts before writing code. I have strong opinions about the difference between infrastructure that enables people and infrastructure that just keeps the lights on.


What I'm Working On

My current work lives at ergon-automation-labs β€” an org I founded to build Bot Army, a 55+ repo personal operating system for attention management built on Elixir/BEAM, NATS, SaltStack, and a push/pull surface philosophy.

Public Distributions

I share parts of the system that others can use:

Transparency

β†’ See the full project portfolio at ergon-automation-labs


This Repo

Older personal projects, experiments, and prior work live here β€” spanning distributed systems, observability tooling, Kubernetes, AWS/GCP, security, and AI tooling built during my time at Filevine and before.

Notable prior work:

  • AI SRE Terminal β€” LLM-powered on-call workflow tool built at Filevine, adopted organically by teammates
  • Algorithmic trading platform β€” early distributed systems work at scale
  • Various Kubernetes, cloud infra, and observability experiments over 25 years

How I Think

  • Schema-first. Contracts between services are interfaces between teams.
  • Push vs. pull is a design decision. Interrupts should earn their interruption.
  • Operational clarity is a feature. If on-call is miserable, the system has a design problem.
  • Boring technology is a deliberate choice. I reach for interesting technology when the problem actually demands it.

Currently Open To

Staff / Principal Platform Engineering roles at AI-native companies in the Denver area or remote.

If my work resonates, let's talk.


Last updated March 2026

Popular repositories Loading

  1. dotfiles dotfiles Public

    Forked from desheffer/dotfiles

    My dotfiles

    Vim Script 3 1

  2. test_mcp_client test_mcp_client Public

    Python 3

  3. ai-ide-api ai-ide-api Public

    Python 3

  4. notion_notes notion_notes Public

    JavaScript 1

  5. portable-doom-emacs portable-doom-emacs Public

    Making my doom emacs install portable

    Makefile 1

  6. games_test_ollama games_test_ollama Public

    A test at feeding Ollama a few pdf documents and asking it questions about the docs

    Jupyter Notebook 1