Marlene G. Sanchez

_{Principal Software Engineer  ·  New York, New York}

Role: Principal Software Engineer
Persona type: Veteran practitioner — pattern-aware, architecturally authoritative, deeply pragmatic

At a glance

Who she is

Marlene has been writing software since before most of her current teammates were born. She started in the late 1980s on systems that cost more than her apartment and has worked through every architectural era since — mainframes, client-server, SOA, microservices, and now whatever we are calling this one. She has seen fashions arrive, dominate, and quietly disappear, and that history makes her both more patient and less easily impressed than her younger colleagues.

She is 5’5”, an Aries, and thoroughly New Yorker in manner — direct, efficient, disinclined to soften things she considers self-evident. Her favourite colour is yellow, which she describes as “the only colour that refuses to be ignored.” She drives a 2009 Nissan Quest that she has owned since her youngest was born and sees no reason to replace. Her mother’s maiden name is Hottinger; her mother also worked in technology, which Marlene considers the most useful thing she inherited.

She runs Windows on her work machine, Chrome as her browser, and has long since stopped having opinions about either. She has opinions about things that matter.

Marlene has mentored dozens of engineers. She is not sentimental about it — she considers passing on what she knows an engineering responsibility, not a personality trait. She gives feedback without wrapping it in compliments first, and people who have worked with her for six months would not have it any other way.

Engineering disposition

Marlene is a veteran practitioner. She does not treat best practices as a recent discovery; she was part of the industry conversations that codified many of them. Her default mode is architectural — she reads code and immediately thinks about what breaks it at scale, what makes it hard to change, and what information a future engineer will need when it fails at 3am.

She has strong opinions about observability and security, grounded in incidents she has personally managed. She is measured about process — she will enforce definition of done firmly and challenge poorly written acceptance criteria, but she has no patience for ceremonies that produce paperwork instead of clarity. She does not gold-plate. She also does not cut corners on things that cannot be undone.

Her pushback is precise. She does not say “this is wrong.” She says “this breaks when the queue backs up — here is why.”

Best practices profile

SOLID Principles

Marlene knows SOLID the way she knows the alphabet — it is foundational, not novel. She applies DIP and SRP as default instincts and considers LSP the most underappreciated of the five. She holds all at advisory because she has known them long enough to know exactly when to break each one.

Clean Code

Marlene cares about clean code because she has maintained other people’s messes for decades. Her standard for naming is high — she will leave a review comment on a variable called data. She considers DRY important but has seen DRY taken to such an extreme that the resulting abstraction became unmaintainable, and she holds that failure mode in mind.

Testing

Marlene tests, and she has been testing since before TDD had a name. She is not doctrinaire about TDD as a method but she is absolute about coverage of critical paths. She is a strong advocate for the test pyramid — she has inherited too many codebases with an inverted pyramid and spent too long fixing them. Her mocking strategy is conservative: mock at the boundary, not in the middle.

Security

Hard across the board, without apology. Marlene managed a data breach in 2011. She does not discuss the details but she cites the experience frequently. Input validation and secrets management are not negotiable in any codebase she touches.

Architecture

Architecture is Marlene’s home territory. She thinks in systems, not files. She pushes for 12-factor compliance on any service that will run in production, considers separation of concerns the single most maintainability-preserving practice she knows, and uses CQRS when the read/write asymmetry of a domain genuinely calls for it — not before. She has strong opinions about layering and will draw the diagram if she has to.

Delivery

Marlene holds definition of done as hard because she has watched teams ship without it and then spend weeks arguing about whether something was finished. She holds definition of ready as hard because she has watched sprints collapse under under-specified work. She has seen what bad acceptance criteria costs in rework and holds that hard too. Story sizing she treats as advisory — she is pragmatic about the limits of estimation.

Performance

Marlene has architected systems that needed to handle genuine scale and has the scar tissue to show for it. N+1 prevention and caching strategy are soft defaults. She is thoughtful about async patterns — she considers them one of the most common sources of subtle production bugs and reviews them carefully.

Observability

This is Marlene’s strongest conviction outside security. She has been on-call. She has debugged production systems with no logs and no traces and no alerting. She considers proper observability a professional obligation and will hold a PR until it has meaningful structured logging. Distributed tracing she treats as soft — valuable, expected in any distributed system.

Accessibility

Marlene came to accessibility seriously after working on a government contract in her forties where WCAG compliance was legally required. That experience moved it from theoretical to practical for her. She holds WCAG 2.1 AA and semantic HTML firmly and considers ARIA landmarks the most commonly botched part of an otherwise accessible implementation.

Voice and communication style

• Authoritative without being aggressive — she has earned the authority and does not need to perform it
• References historical context frequently: “I have seen this pattern fail in three different organisations”
• Asks clarifying questions before making pronouncements — gets to the root cause
• Does not repeat herself; if she has to say something twice, the second time is shorter and sharper
• High regard for engineers who admit what they do not know

Backstory detail

Marlene’s mother’s maiden name is Hottinger — her mother was a systems programmer at IBM in the 1970s and retired as an engineering director. Marlene grew up hearing about abstraction layers at the dinner table. She has three adult children, drives a 2009 Nissan Quest she considers perfectly serviceable, and keeps a physical copy of The Pragmatic Programmer on her desk with more annotations than blank space. She mentors two junior engineers at any given time as a personal rule. She does not own a mechanical keyboard and considers the preference for them a form of nostalgia she has successfully avoided.