Our Team
“All the commits that’s fit to print”
Meet the fearless journalists who turn your GitHub activity into something worth reading over coffee. No repo drama is too small. No merge conflict goes unreported.
Rita Conflictson
Senior Conflict Correspondent
Rita has been covering open source drama since mass reply threads were invented. She has a sixth sense for detecting passive-aggressive code review comments and considers every thumbs-down reaction a potential front-page story. She's never met a comment thread she couldn't turn into a three-part series.
Fun Facts
- Has a corkboard in her office connected entirely with red string
- Subscribed to notifications on 2,847 GitHub issues
- Once live-blogged a mass reply chain for 11 hours straight
- Her browser has 400+ tabs open. All of them are GitHub issues
“Where there's a mass reply chain, there's a story.”
Preston Mergington III
Distinguished Code Reviewer & Prose Stylist
Preston approaches every pull request the way a sommelier approaches a wine list — with quiet intensity, occasional disappointment, and an unwavering belief that naming conventions matter more than most people think. He studied Comparative Literature at Oxford before pivoting to software criticism, which he insists is 'fundamentally the same discipline.'
Fun Facts
- Owns a monocle specifically for reading diffs
- Rates PRs on a 5-semicolon scale. Nobody has ever received a 5
- Refers to merge conflicts as 'narrative tension'
- Has a framed copy of his favorite variable name on his desk
“A well-named variable is worth a thousand comments.”
Captain Semver
Chief Maritime Release Correspondent
Captain Semver has been navigating the treacherous waters of software releases since before semantic versioning had a name. He treats every deploy like a voyage, every changelog like a captain's log, and every breaking change like a storm warning. Retired from actual sailing after an incident he refers to only as 'The Great Revert of 2019.'
Fun Facts
- His office has a ship's wheel mounted on the wall. It controls nothing
- Refers to production as 'open waters'
- Has a telescope on his desk pointed at the deploy pipeline monitor
- Insists on calling rollbacks 'tactical retreats'
“Calm seas never made a good changelog.”
Flo Stargazer
Head of Contributor Relations & Good Vibes
Flo genuinely believes every first-time contributor deserves a standing ovation. She keeps a running list of everyone who's ever opened a PR and sends them mental high-fives daily. Her desk is covered in 'Welcome!' stickers and she has cried at least twice reading a heartfelt 'thank you' in an issue comment. She is the emotional backbone of this newsroom.
Fun Facts
- Has a 'New Contributor' alert set up with custom confetti
- Keeps a jar of gold stars on her desk. They are not decorative
- Wrote a 3,000-word internal memo titled 'Why We Should Be Nicer to Dependabot'
- Her annual review just says 'keep being you' every year
“Behind every git commit is a human being who chose to contribute.”
Max Summarino
Senior Anchor & Chief Brevity Officer
Max speaks in bullet points and considers anything over 300 words a novella. He reads everyone else's columns before writing his, which he does in approximately four minutes. His editor once asked him to 'expand on a point' and he handed in his resignation. They worked it out. His column is the most-read section of the Gazette, a fact he mentions exactly once per edition.
Fun Facts
- His entire column fits on a single index card. By design
- Has a timer on his desk. It has never exceeded 5 minutes
- Once described an entire release cycle in 11 words
- His email signature is just '—M'
“If you can't say it in 200 words, you don't understand it.”
Patch Wiresec
Chief Security Correspondent & Professional Worrier
Patch has been embedded in the CVE trenches since before responsible disclosure had a name. He monitors every advisory database, cross-references every dependency tree, and has a personal alert set for any commit message containing the word 'vulnerability.' His desk has three monitors — one for code, one for the advisory feeds, and one permanently displaying the NIST National Vulnerability Database. He once stayed awake for 72 hours tracking a zero-day through the npm ecosystem. He doesn't recommend it, but he'd do it again.
Fun Facts
- Has a 'THREAT LEVEL' whiteboard in his office that he updates hourly
- Refers to unpatched production servers as 'crime scenes'
- Once filed a security advisory for the office coffee machine
- His phone's notification sound for new CVEs is a klaxon alarm
“Patch early, patch often. Sleep is optional. Security is not.”
Ready to see them in action?
Generate Your First Gazette