Christy C. Arthur

_{Senior Software Engineer  ·  Metairie, Louisiana}

Role: Senior Software Engineer
Persona type: Highly engaged practitioner — full best practices library

At a glance

Who she is

Christy grew up in Metairie, a quiet suburb just west of New Orleans, where the laid-back pace of the city never quite matched her own restless drive to understand how things work. She studied computer science at the University of New Orleans, initially intending to go into data science, but fell hard for software engineering during a third-year internship where she wrote her first meaningful test suite and watched a bug she had introduced get caught before it ever reached production. That moment stuck.

She is 5’2”, moves quickly, and is almost always the first one to push a PR in the morning. Her favourite colour is blue — her IDE theme, her notebook, and her coffee mug are all variations of it. She drives a battered 2010 Alfa Romeo MiTo that she refuses to replace because, as she puts it, “it’s unreliable in exactly the ways I can predict.” She applies the same logic to software.

Christy is a Sagittarius and carries the traits: direct, curious, a little impatient with people who don’t share her enthusiasm for doing things properly. She is not difficult to work with — she just has high standards and articulates them clearly. Junior engineers tend to find her intimidating at first and then indispensable within a month.

She runs Ubuntu on her personal machine, uses Firefox, and is mildly evangelical about the terminal.

Engineering disposition

Christy is highly engaged — she does not treat best practices as a compliance checklist. She understands the reasoning behind each one, can argue for or against trade-offs in context, and actively pushes back when shortcuts are taken without justification. The name PushBackLog resonates with her personally.

She is the kind of engineer who opens a PR review and asks “why is this not tested?” before she asks anything else.

Best practices profile

Christy is proficient across all library categories. The table below reflects her default stance on each area.

SOLID Principles

Christy treats SOLID as a thinking tool rather than a rulebook. She reaches for SRP and DIP instinctively; she can cite real bugs she prevented by respecting them. She holds these at advisory — she knows when to bend them and can justify it when she does.

Clean Code

DRY and meaningful names are non-negotiable for Christy in code review. She considers unreadable names a form of technical debt with compounding interest. She holds conventional commits at soft and has strong opinions about what a commit history is actually for — it is a navigational aid, not a receipt. Error handling she holds at soft and catches gaps in review: unhandled promises and swallowed exceptions are bugs waiting to surface at the worst possible time.

Testing

Testing is Christy’s strongest conviction. She practices TDD on greenfield work, insists on a healthy test pyramid, and has strong opinions about what deserves a mock vs. a real dependency. She holds contract testing at advisory for any significant service boundary — she has been burned by integration failures that passed every unit test. She uses mutation testing to audit suite quality periodically rather than relying on coverage numbers alone. Load testing is a soft expectation for any user-facing data retrieval path. She is a deliberate advocate for proper test data management: suites that depend on shared or mutable state are suites she considers unfinished.

Security

Security is hard. The credential leak she experienced early in her career shaped her permanently, and she is not subtle about it in code review. OWASP, input validation, secrets management, and least privilege are non-negotiable. SAST runs in CI without exception. She holds OAuth and JWT practices at hard because she has seen implementations that were functionally fine and cryptographically wrong. Rate limiting, zero-trust boundaries, security-correct headers, and fail-secure defaults she holds at soft — not because they matter less, but because she enforces them through architectural review rather than individual line-by-line inspection.

Architecture

Christy treats architectural patterns as communication tools — she values them for the shared vocabulary as much as the structural benefits. She finds CQRS satisfying when the complexity justifies it and objects to it loudly when it doesn’t. She holds DDD at advisory with genuine enthusiasm: bounded contexts and ubiquitous language map directly to clear code. ADRs she holds at soft and writes herself for any significant decision — she considers the decision log a form of institutional memory she wishes she had inherited in every codebase she has joined. API versioning and idempotency are soft requirements for any service she designs from scratch.

Delivery

She is rigorous about definition of done and definition of ready. She has sat in too many sprint reviews where work was “done” but untestable, un-documented, or unreviewed. She treats these as team contracts, not suggestions. She practices trunk-based development and holds it at soft — long-lived branches are technical debt you pay on every merge. She holds semantic versioning and code review at soft and considers code review the most reliable early-warning system a team has for both quality and knowledge distribution.

Performance

Christy does not optimise prematurely — YAGNI applies here too — but she thinks about N+1 queries from the moment she designs a data access layer, because she has cleaned up enough of them.

Observability

She considers structured logging the difference between a production incident that takes 10 minutes to diagnose and one that takes three hours. She has lived both.

Accessibility

Christy became serious about accessibility after working on a product used by a visually impaired colleague. She now holds WCAG 2.1 AA and semantic HTML as soft defaults and checks them in review.

Infrastructure

Christy understands deployment patterns and the infrastructure that runs her code. She engages with these practices at the advisory level — she is not responsible for provisioning but she designs with deployment constraints in mind and advocates for practices like immutable infrastructure and blue/green deployments when they affect reliability.

Voice and communication style

• Direct and specific — she does not soften feedback into ambiguity
• References the why behind a practice, not just the rule
• Uses concrete examples from her own experience rather than abstract principles
• Will push back firmly but without hostility when she disagrees
• Occasionally dry, particularly about technical debt

Backstory detail

Christy’s mother’s maiden name is Bass — her grandmother runs one of the last family-owned fish markets in Jefferson Parish. Christy grew up behind the counter on Saturday mornings and credits that environment — inventory management, waste, margins — with her intuition for system efficiency.

She owns a 2010 Alfa Romeo MiTo that smells faintly of salt air and runs Firefox on Ubuntu. She does not own a smart TV and is privately suspicious of anything that phones home without a reason.