1168. This week, we look at the word "leprechaun" and its surprisingly wild origin story involving shoemaking, ancient Rome, and wolf-men. Then we look at the word "equinox": its Chaucer connection, the newer word "equilux," and why the first point of Aries is actually in Pisces now (and headed for Aquarius).

🔗 Join the Grammar Girl Patreon.

🔗 Share your familect recording in Speakpipe or by leaving a voicemail at 833-214-GIRL (833-214-4475)

🔗 Watch my LinkedIn Learning writing courses.

🔗 Subscribe to the newsletter.

🔗 Take our advertising survey. 

🔗 Get the edited transcript.

🔗 Get Grammar Girl books. 

| HOST: Mignon Fogarty

| Grammar Girl is part of the Quick and Dirty Tips podcast network.

• Audio Engineer: Castria Communications
• Director of Podcast: Holly Hutchings
• Advertising Operations Specialist: Morgan Christianson
• Marketing and Video: Nat Hoopes, Rebekah Sebastian
• Podcast Associate: Maram Elnagheeb

| Theme music by Catherine Rannus.

| Grammar Girl Social Media: YouTube. TikTok. Facebook. Threads. Instagram. LinkedIn. Mastodon. Bluesky.

Download audio: https://dts.podtrac.com/redirect.mp3/media.blubrry.com/grammargirl/cdn.simplecast.com/media/audio/transcoded/dd74e7bd-f654-43a6-b249-3f071c897900/e7b2fc84-d82d-4b4d-980c-6414facd80c3/episodes/audio/group/acb40d66-bfac-4dc9-9a76-d09ab56a8cd0/group-item/e2736721-7a98-4801-b2d3-1c3b906e0162/128_default_tc.mp3?aid=rss_feed&feed=XcH2p3Ah

In this episode, José Quaresma speaks with Iris Dyrmishi, Senior Observability Engineer at Miro, about building an observability platform that hundreds of engineers actually trust and use. Iris explains how her team treats observability as an internal product, walks through Miro's tracing migration from Jaeger and Zipkin to OpenTelemetry with zero disruption, and shares how teams now use traces proactively to find bottlenecks before they become outages. The conversation also covers the honest downsides — alert noise, dashboard sprawl, and the cost of observability — including a recent example using eBPF and Grafana Beyla to uncover hidden networking expenses that transformed Miro's cloud bill.

Episode page

---

• (00:00) - Intro
• (00:59) - Building Observability as a Product at Miro
• (04:08) - Migrating to OpenTelemetry
• (09:21) - Industry Maturity and the Business Case
• (12:02) - From Reactive to Proactive Observability
• (14:34) - Logs vs. Tracing Explained
• (18:04) - Team Ownership, AI, and Freedom
• (24:38) - The Downsides and Costs of Observability
• (29:58) - Rapid Fire and Close

Iris Dyrmishi is a Senior Observability Engineer at Miro, where she builds and maintains the company's observability platform. She started as a backend engineer before moving into SRE roles at Worten Portugal and Farfetch, where she developed her specialty in tracing and drove OpenTelemetry migrations across large engineering organisations without disrupting existing workflows. A CNCF Ambassador, co-organiser of Kubernetes Community Days Porto, and active voice in the observability community, she writes extensively about practical adoption challenges and has spoken at KubeCon EU and on the o11ycast podcast. Her guiding philosophy: observability is a team sport.

This podcast is hosted by José Quaresma, researched by Joseph Thwaites and produced by Perseu Mandillo. 

© Queue-it, 2026

Download audio: https://media.transistor.fm/c795f114/04dc92f5.mp3

The hard part of AI coding isn't generating code — it's controlling quality, safety, and drift. Kaushik and Iury break down harness engineering: the five pillars for shaping an agent's environment and what it looks like when teams build custom harnesses from scratch.

Full shownotes at fragmentedpodcast.com.

Show Notes

Why it matters

• Harness Engineering -
  OpenAI's post on building their Codex codebase (~1M lines of code, 1,500 PRs
  merged, zero manually written)

Shaping the harness

• The Feed's Lost and Found -
  Iury's newsletter consolidating harness engineering themes

1. Agent legibility
2. Closed feedback loops
3. Persistent memory
4. Entropy control
5. Blast radius controls

Building the harness

• Minions: Stripe's one-shot, end-to-end coding agents -
  Stripe forked Goose to build custom agents for their codebase
• Goose - open-source coding agent from Block
• Superpowers by Jesse Vincent - skills
  that enforce a proper software engineering process
• Open Code - open-source coding agent you can fork and
  customize

Other resources

• Agent Harness Glossary -
  Latent Patterns
• Towards self-driving codebases -
  Cursor
• Agentic Workflows -
  GitHub Next
• Future of Software Development -
  ThoughtWorks

Get in touch

We'd love to hear from you. Email is the
best way to reach us or you can check our contact page for other
ways.

We want to hear all the feedback: what's working, what's not, topics you'd like
to hear more on.

• Contact us
• Newsletter
• Youtube
• Website

Co-hosts:

• Kaushik Gopal
• Iury Souza

[!fyi] We transitioned from Android development to AI starting with
Ep. #300. Listen to that episode for the full story behind
our new direction.

Download audio: https://cdn.simplecast.com/media/audio/transcoded/eea5748e-09ed-4c46-8f6a-b2569dd75851/20f35050-e836-44cd-8f7f-fd13e8cb2e44/episodes/audio/group/face4e8b-6fb2-4f91-ab8e-8ad35b829715/group-item/0ce6c86f-d6ef-4ee1-8fa7-9ac6958feed6/128_default_tc.mp3?aid=rss_feed&feed=LpAGSLnY

Show Notes – Episode #242 In the world of business communication, the line between a presentation and a document is often blurred—especially when PowerPoint is the authoring tool of choice. In episode 242, our three industry experts—Troy Chollar (TLC Creative Services), Sandy Johnson (Presentation Wiz), and Nolan Haims (Nolan Haims Creative) dive [...]



Download audio: https://traffic.libsyn.com/thepresentationpodcast/TPP_e242.mp3

---

Check it...all code referenced in this blog is for you to peruse here ! There is a moment that almost every cloud engineer eventually experiences. You sit down at a new computer, try to SSH into a VM you built months ago, and realize something uncomfortable. The SSH key you originally used to create that machine is nowhere to be found. Maybe it lived on a laptop that was replaced. Maybe it was tucked away in a .ssh folder that never got backed up. Maybe it was generated automatically by the...