Contributors

Reza Mokhtari is a senior practitioner writer at Stack Quarterly. He spent the better part of a decade as a backend and platform engineer at a series of small-to-mid software teams before pivoting full-time into the writing side of the craft. His beat at Stack Quarterly is the practical mechanics of agentic orchestration: how teams structure multi-agent workflows, how they decide when an LLM call should become a tool call, where memory belongs in the architecture, and which abstractions hold up under real load.

Reza’s posture is the one most of his readers share. He has seen enough new tools in his career to be skeptical of any pitch that sells velocity without explaining maintenance. He writes long, but not for the sake of length. He prefers a piece that walks through a working example end-to-end over a piece that lists ten frameworks without trying any of them. When he writes about a tool he likes, he says what he disagrees with about it. When he writes about a tool he does not like, he explains the use cases where he would still pick it.

Off Stack Quarterly, Reza maintains a personal blog of practitioner notes and contributes occasional patches to a small set of open-source orchestration libraries. He is based in a midsize European city and writes from his own apartment, on his own time, on his own opinions.

Ginger Wolfe-Suarez is a staff developer-essayist at Stack Quarterly. Her beat is the workflow side of the developer life: how teams actually adopt the agentic patterns the industry is loudly recommending, what the rollout looks like inside a real engineering org, which “default” stack choices deserve to keep their slot, and which ones quietly become the thing the team most wants to rip out. She writes with a lighter hand than Reza but no less rigorously.

Ginger has spent most of her career embedded in product-engineering teams of fewer than fifteen people. She has been the engineer who has had to make the calls in this piece, and she writes from that vantage. Her essays at Stack Quarterly tend to braid two threads: a specific architectural observation about a tool or pattern, and a wider observation about what the choice signals about the team that made it. She has a soft spot for tools that respect the practitioner’s time and a sharp pen for ones that confuse “magic” with “good defaults.”

Outside Stack Quarterly, Ginger runs a small editorial side project on developer workflow and is a frequent reviewer of friends’ technical drafts. She writes from her own home office and is paid by Stack Quarterly’s parent for her writing here. She does not consult for the vendors she covers.

The Editorial Team byline at Stack Quarterly covers landscape pieces, listicles, and surveys where the conclusions reflect the judgement of the publication as a whole rather than a single named writer. Three or four people sit behind that byline at any given time: a rotating mix of the named contributors above plus the publication’s editor and a research lead.

When the Editorial Team byline runs, it means the piece has been argued through in a room. Pieces under the Editorial Team byline are landscape surveys (the “what teams are running” pieces), listicles where multiple practitioners contributed picks, and the “decision-piece” essays where the publication takes a deliberate position on a stack question. The Editorial Team byline never runs on case-study or interview pieces — those carry a named author who took the lead. Like the named contributors, the Editorial Team writes from independence: editorial control sits with the named bylines, not with the publication’s parent. Corrections are owned by whoever wrote the line in question.

For corrections, tips, or pitches: editorial @ stackquarterly.com.