Google Updates Stitch and Introduces “Vibe Design” - DTNS 5229

March 19, 2026·31 min·1 clip

Key insight from segment 5

The usable center is technical. Once the ad-heavy edges pass, the clip settles into lint warnings, formatters, and why teams stop handling standards by hand. Yes, tabs versus spaces comes up. One host treats formatting as a relief, because nobody wants to police every space or tab. The joke stays dry. Another calls tabs versus spaces a spiritual debate, then chooses spaces without wobbling. Linters come across as plain teamwork tools. Not glamorous, just useful when a team needs coding standards and fewer tiny chores. The uncertainty helps. The hosts admit they do not know exactly how Ruff works, or where lint got its name. That lands better than fake certainty. They connect the category to everyday developer pain in Python, Java, and Kotlin. Writing linters sounds like a grind, especially in Java and Kotlin. Then OpenAI comes in. The question shifts from one tool to whether OpenAI will keep an open source platform open in practice. Android experience shapes the read. Since the hosts know AOSP and Google, they test OpenAI's stated plan against a culture they understand. No verdict gets jammed into place. It ends with a careful shrug: curious about commitment, not pretending to predict it.

As heard by us

A practical look at linting, formatters, tabs versus spaces, and the open-source question around OpenAI.

The discussion stays grounded in coding basics: lint warnings, formatters, and the old tabs-versus-spaces argument. It also makes a plain case for linters in team work, since they help set standards and take a few routine calls off the table.

Read the full review in PlayNext →

Why you'd press play

If you care about AI tools meeting real developer habits, start here.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Daily Tech News Show