What are the key takeaways from this Go Time episode?

Key insights include: **Manager Communication:** Avoid sending multiple "what's the status" messages daily - establish clear update agreements (daily/weekly) instead of creating developer anxiety with constant status requests.; **Type Safety Benefits:** Non-typed languages become dangerous at scale - Pinterest experienced production bugs from variable reuse that Go's type system would have prevented, saving three debugging days.; **Manual Work Strategy:** Grinding through tasks manually before automating proves more effective - understand processes thoroughly first, then determine if automation is worthwhile or if assisted approaches work better.

What did Kurt Mackey and Nishant Roy discuss on Go Time?

Go Time reviews 2022's most popular and unpopular opinions from 76 submissions, revealing developer preferences on management practices, programming languages, and surprisingly controversial food choices. Key topics include: **Manager Communication:** Avoid sending multiple "what's the status" messages daily - establish clear update agreements (daily/weekly) instead of creating developer anxiety with constant status requests.; **Type Safety Benefits:** Non-typed languages become dangerous at scale - Pinterest experienced production bugs from variable reuse that Go's type system would have prevented, saving three debugging days..

How long is this episode of Go Time?

This episode is 37 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

Go Time

Unpop roundup! 2022

October 9, 2024

37 min episode · 2 min read

Kurt Mackey,Nishant Roy,Inbal Cohen

Episode

37 min

Read time

2 min

Topics

Leadership, Software Development, Product & Tech Trends

AI-Generated Summary

Published Dec 19, 2025

Key Takeaways

✓Manager Communication: Avoid sending multiple "what's the status" messages daily - establish clear update agreements (daily/weekly) instead of creating developer anxiety with constant status requests.
✓Type Safety Benefits: Non-typed languages become dangerous at scale - Pinterest experienced production bugs from variable reuse that Go's type system would have prevented, saving three debugging days.
✓Manual Work Strategy: Grinding through tasks manually before automating proves more effective - understand processes thoroughly first, then determine if automation is worthwhile or if assisted approaches work better.
✓Opinion Polling Patterns: 52 of 76 opinions were popular versus 20 unpopular, suggesting hosts should encourage more controversial takes using definitive language like "best" rather than qualifiers.

What It Covers

Go Time reviews 2022's most popular and unpopular opinions from 76 submissions, revealing developer preferences on management practices, programming languages, and surprisingly controversial food choices.

Key Questions Answered

•Manager Communication: Avoid sending multiple "what's the status" messages daily - establish clear update agreements (daily/weekly) instead of creating developer anxiety with constant status requests.
•Type Safety Benefits: Non-typed languages become dangerous at scale - Pinterest experienced production bugs from variable reuse that Go's type system would have prevented, saving three debugging days.
•Manual Work Strategy: Grinding through tasks manually before automating proves more effective - understand processes thoroughly first, then determine if automation is worthwhile or if assisted approaches work better.
•Opinion Polling Patterns: 52 of 76 opinions were popular versus 20 unpopular, suggesting hosts should encourage more controversial takes using definitive language like "best" rather than qualifiers.

Notable Moment

The most unpopular opinion wasn't about programming but yogurt dislike, earning 97% disagreement and demonstrating how food preferences can be more divisive than technical debates.

Know someone who'd find this useful?