Listenly

How should non-native English speakers contribute to PHP internals discussions using AI translation?

Answered at 6:00 in Community Corner Podcast: This Week in PHP Internals with Len Woodward · PHP[Podcast]: Episodes from PHP[Architect]

— questions searchable right now

How should non-native English speakers contribute to PHP internals discussions using AI translation?

Non-native English speakers should use deterministic translation tools like Google Translate rather than LLMs, write their response in their original language, translate it, and then attach both the original message and the translated message to their post. This prevents AI from overriding their phrasing and making arguments for them, which has been a concern in PHP internals discussions.

Len Woodward on PHP[Podcast]: Episodes from PHP[Architect]All answers from this podcast →
Full answer and detailsRead the whole answer, key facts and every other question from this episode

In short

Non-native English speakers should use deterministic translation tools like Google Translate rather than LLMs, write their response in their original language, translate it, and then attach both the original message and the translated message to their post.

Len Woodward, Host of This Week in PHP Internals at Project Gopher Multimedia · Community Corner Podcast: This Week in PHP Internals with Len Woodward · PHP[Podcast]: Episodes from PHP[Architect] · answer at 6:00

Key takeaways

  • Non-native English speakers should use deterministic translation tools like Google Translate rather than LLMs, write their response in their original language, translate it, and then attach both the original message and the translated message to their post.

Quote to remember

“I used AI to help me summarize but I still went through three hours of script revisions, I still recorded it, I still edited it.”

— Len Woodward

The full answer · about 2 min

Non-native English speakers should use deterministic translation tools like Google Translate rather than LLMs, write their response in their original language, translate it, and then attach both the original message and the translated message to their post. This prevents AI from overriding their phrasing and making arguments for them, which has been a concern in PHP internals discussions.

Key facts

  • Between a dozen to two to three dozen separate threads per week on PHP internals mailing list
  • Episodes of This Week in PHP Internals: approximately 10 minutes during feature freeze periods, up to 20-22 minutes during active discussion periods
  • Len Woodward has been writing code since 2013
  • Project Gopher Multimedia established in 2021
  • Approximately four months before the podcast launch: Brent Roos YouTube video that inspired the series

People, companies and topics mentioned

This Week in PHP InternalsPHP Architect Community CornerProject Gopher MultimediaArtisan BuildPHP internals mailing listBrent RoosLaravelLarry Garfield

More answers from this episode

 ·  All answers from PHP[Podcast]: Episodes from PHP[Architect] →
—
—
0:00
0:00