What are the key takeaways from this The Changelog episode?

Key insights include: **Political Influence Strategy:** Maintain 10-15 brief project write-ups ready to deploy when organizational priorities shift. Wait for reliability waves after incidents or feature waves during growth periods, then present pre-prepared proposals that align with current executive focus rather than constantly campaigning for single ideas.; **Code Review Excellence:** Limit comments to six or fewer per review to maintain focus on high-level architectural concerns. Review the entire codebase context, not just the diff, to identify missing implementations or better existing solutions the author overlooked. This approach provides significantly more value than line-by-line nitpicking.; **Engineering Taste Framework:** Define taste as alignment between personal values (reliability, performance, accessibility, code organization) and project requirements. Good taste means flexibly adjusting value priorities to match specific project contexts rather than rigidly applying universal standards. Taste becomes more valuable as AI handles technical execution.

What did Sean Gedicki discuss on The Changelog?

Sean Gedicki, staff engineer at GitHub, discusses navigating company politics as a senior engineer, avoiding worry-driven development, defining good taste in software engineering, the impact of agentic coding, and strategies for writing blog posts that reach Hacker News front page. Key topics include: **Political Influence Strategy:** Maintain 10-15 brief project write-ups ready to deploy when organizational priorities shift. Wait for reliability waves after incidents or feature waves during growth periods, then present pre-prepared proposals that align with current executive focus rather than constantly campaigning for single ideas.; **Code Review Excellence:** Limit comments to six or fewer per review to maintain focus on high-level architectural concerns. Review the entire codebase context, not just the diff, to identify missing implementations or better existing solutions the author overlooked. This approach provides significantly more value than line-by-line nitpicking..

How long is this episode of The Changelog?

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

The Changelog

DO repeat yourself! (Interview)

November 12, 2025

79 min episode · 2 min read

Sean Gedicki

Episode

79 min

Read time

2 min

Topics

Productivity, Leadership, Artificial Intelligence

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓Political Influence Strategy: Maintain 10-15 brief project write-ups ready to deploy when organizational priorities shift. Wait for reliability waves after incidents or feature waves during growth periods, then present pre-prepared proposals that align with current executive focus rather than constantly campaigning for single ideas.
✓Code Review Excellence: Limit comments to six or fewer per review to maintain focus on high-level architectural concerns. Review the entire codebase context, not just the diff, to identify missing implementations or better existing solutions the author overlooked. This approach provides significantly more value than line-by-line nitpicking.
✓Engineering Taste Framework: Define taste as alignment between personal values (reliability, performance, accessibility, code organization) and project requirements. Good taste means flexibly adjusting value priorities to match specific project contexts rather than rigidly applying universal standards. Taste becomes more valuable as AI handles technical execution.
✓Senior Engineer Confidence: Staff engineers must confidently advocate for technical directions even with internal uncertainty, as they possess the best available information for decisions. Representing technical expertise to the organization is a core responsibility, not optional. Confidence develops naturally through years solving similar problems across codebases.
✓Blog Amplification Tactics: Craft titles punchy enough to generate upvotes without reading but restrained enough to avoid triggering Hacker News flame war detection (more comments than upvotes). Target academic tone with slight colloquialism. Accept that low-engagement readers amplify signal to reach high-quality readers who provide valuable feedback.

What It Covers

Sean Gedicki, staff engineer at GitHub, discusses navigating company politics as a senior engineer, avoiding worry-driven development, defining good taste in software engineering, the impact of agentic coding, and strategies for writing blog posts that reach Hacker News front page.

Key Questions Answered

•Political Influence Strategy: Maintain 10-15 brief project write-ups ready to deploy when organizational priorities shift. Wait for reliability waves after incidents or feature waves during growth periods, then present pre-prepared proposals that align with current executive focus rather than constantly campaigning for single ideas.
•Code Review Excellence: Limit comments to six or fewer per review to maintain focus on high-level architectural concerns. Review the entire codebase context, not just the diff, to identify missing implementations or better existing solutions the author overlooked. This approach provides significantly more value than line-by-line nitpicking.
•Engineering Taste Framework: Define taste as alignment between personal values (reliability, performance, accessibility, code organization) and project requirements. Good taste means flexibly adjusting value priorities to match specific project contexts rather than rigidly applying universal standards. Taste becomes more valuable as AI handles technical execution.
•Senior Engineer Confidence: Staff engineers must confidently advocate for technical directions even with internal uncertainty, as they possess the best available information for decisions. Representing technical expertise to the organization is a core responsibility, not optional. Confidence develops naturally through years solving similar problems across codebases.
•Blog Amplification Tactics: Craft titles punchy enough to generate upvotes without reading but restrained enough to avoid triggering Hacker News flame war detection (more comments than upvotes). Target academic tone with slight colloquialism. Accept that low-engagement readers amplify signal to reach high-quality readers who provide valuable feedback.

Notable Moment

An intern at TikTok saved the company $300,000 annually by rewriting one heavily-used endpoint from Go to Rust, eliminating garbage collection pauses. This demonstrates how identifying the right optimization point delivers massive leverage regardless of seniority, making strategic focus more valuable than grinding effort.

Know someone who'd find this useful?

Episode Transcript

Hello and welcome. I'm Jared and you are listening to the change log where each week we interview the hackers, the leaders, and the innovators of the software world to pick their brains, to learn from their failures, to get inspired by their accomplishments, and to have a lot of fun along the way. On this episode, prolific software blogger, Sean Gedicki, joins us to discuss why he believes software engineers need to be more involved in the politics of their organization, how to avoid worry driven development, what is good taste in software engineering, where agentic coding will take our industry, why getting the main thing right is so important, and how to get your blog to the top of hacker news. But first, a big thank you to our partners at fly.io, the public cloud built for developers who ship. We love fly. You might too. Learn more at fly.io. Okay. Sean, get a key on the change log. Let's do it. Well, friends, agentic Postgres is here and from our friends over at Tiger Data. This is the very first database built for agents and is built to let you build faster. You know, a fun side note is 80% of Claude was built with AI. Over a year ago, 25% of Google's code was AI generated. It's safe to say that now it's probably close to a 100%. Most people I talk to, most developers I talk to right now, almost all their code is being generated. That's a different world. Here's the deal. Agents are the new developers. They don't click. They don't scroll. They call. They retrieve. They parallelize. They plug in your infrastructure to places you need it to perform, but your database is probably still thinking about humans only because that's kind of where Postgres is at. Tiger Data's philosophy is that when your agents need to spin up sandboxes where migrations query huge volumes of vector and text data, well, normal Postgres, it might choke, and so they fix that. Here's where we're at right now. Agentic Postgres delivers these three big leaps, native search and retrieval, instant zero copy forks, and MCP server plus your CLI plus a cool free tier. Now if this is intriguing at all, head over to tigerdata.com. Install the CLI, just three commands, spin up an agentic postgres service, and let your agents work at the speed they expect, not the speed of the old way. The new way, agent to Postgres is built for agents, is designed to elevate your developer experience and build the next big thing. Again, go to tigerdata.com to learn more. Today, we're joined by Sean Gadecki, who is over there in Melbourne, Australia, and has been blogging like a fiend, like a prolific fiend. Not a spa. Been like slurping up his blog post and put him in Change Log News. Sean, welcome. Hey. Great to be here. Well, because you are where you are and we are where …

Get the full transcript (15,381 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Changelog transcripts →