text stringlengths 0 2.68k |
|---|
**Jerod Santo:** \[laughs\] That's a good title. |
**Sean Goedecke:** Well, I didn't call it that initially. I was afraid to call it that, and I turned it down, and I've since kind of punched it up a bit. When you're trying to get your blog read, it's a really interesting thing, because I don't care about volume of readers. What I care about is quality of readers, if y... |
**Jerod Santo:** I do. |
**Sean Goedecke:** If the right 10 people read a post, I wouldn't care about the other 90,000. It's getting it to those people who are going to give you really interesting feedback, who are going to email you with their own experience... That's why I write the blog posts. But you can't do that unless those blog posts g... |
So there is this weird dynamic where you have to kind of be a bit clickbaity, even though the people who you're really writing to don't care about the clickbait ,because otherwise it's not going to get in front of them... If you know what I mean. |
**Jerod Santo:** Right. I do know what you mean. |
**Sean Goedecke:** I didn't anticipate that being a thing... |
**Jerod Santo:** So you have to attract the people that you don't actually care about them reading it, because they will amplify the signal of it loud enough so that it will reach the people who otherwise might not have seen it, and now they're the ones who are actually the high quality readers that you're trying to re... |
**Sean Goedecke:** Yeah. Although I do care about all of my readers. And if you read my posts, I love you. |
**Jerod Santo:** I'm just over here trying to figure out which category am I, what group am I in over here? |
**Sean Goedecke:** To give like a concrete example that I think might make it seem a little bit less arrogant to say this... A lot of the people who are going to upvote your post on Hacker News aren't going to read it. They're going to maybe -- they'll maybe click through and like skim the first sentence, they probably... |
**Jerod Santo:** But you don't want to also across the line, so that the person who actually is the high quality reader, they look at your title and they think "Ah, this guy's a hack. He's just trying to get to the top of Hacker News. I'm not going to read this thing." |
**Sean Goedecke:** It also doesn't work. Like, super-clickbaity titles are not typically that successful on Hacker News. Sometimes they are, but in my experience, it works better to be a little bit lower key. |
**Jerod Santo:** \[01:13:46.29\] Well, I would say we have similar aims here, and I think one of the great things about the Changelog, which we've been doing for a very long time - and we have a niche audience; we're software developers, and so it's a very small group of people... And even among software developers, th... |
**Sean Goedecke:** As a Changelog listener myself, thank you. I'm going to take all that as praise to me specifically as well, but... \[laughs\] Yeah, I agree. You have a you have a great audience. And I certainly really, really treasure the messages I get from readers, the thoughtful messages. |
One thing about blowing up on Hacker News is that you do get a lot of very negative feedback. |
**Jerod Santo:** Yeah, totally. |
**Sean Goedecke:** You do have to have a thick skin. My initial post about how about shipping projects in large tech companies where I was talking about how the process being fundamentally political... There were a lot of comments on that, and have been since basically saying "This man is clearly a psychopath." |
**Jerod Santo:** \[laughs\] |
**Sean Goedecke:** "I would not want to work with him in any capacity. I feel bad for his colleagues. He will destroy any company he works at." I get a lot of comments like that too, which I have to just \[unintelligible 01:15:50.05\] |
**Jerod Santo:** Yeah... Those - I just laugh at stuff like that. That's good stuff. We've been on Hacker News a fair bit of times, and we've got thick skin at this point. You have to. Or you just have to not read it. Now, it's not quite the most icily of software world, but I think that's reserved for the R programmin... |
**Sean Goedecke:** I was really surprised that Reddit was worse than Hacker News. I thought Reddit would be better than Hacker News... It's not. Reddit is so much worse. The comments are so much more negative. |
**Jerod Santo:** Yes. And Reddit has a culture of piling on, especially on jokes, where if one person disses you in a funny way, there'll be reply after reply after reply of like them one upping each other, in like a downward spiral of dirtiness. |
**Sean Goedecke:** It's hard to put yourself out there. I have people like -- like, my resume is public on the site. Any post that gets sufficiently popular, there's a handful of people who go and find my resume and tear it apart. They're like "Oh, he's a staff engineer, but staff engineer at like Zendesk and GitHub. L... |
**Jerod Santo:** "What does that really mean...?" \[laughs\] |
**Sean Goedecke:** It's like, "I don't know, I'm pretty proud of where I am." |
**Jerod Santo:** I was going to say, those are good jobs, dude... |
**Sean Goedecke:** I think so, but... People on the internet are always going to criticize. But I think it's useful having my name out there. It's useful it being me and it not being anonymous. I think that adds to the value, even though it's kind of hard \[unintelligible 01:17:18.24\] |
**Jerod Santo:** A hundred percent. The only problem is I've been pronouncing your name Sean Goedecke in my head, and now, after years of reading you, I know it's Sean Goedecke. And so when I say that the next time you're on Changelog News, I will be sure to pronounce it right. Sean, keep writing, man... Keep writing s... |
**Sean Goedecke:** No, that's it. Just thanks to everyone for reading. As long as people keep reading, I'm going to keep writing. |
**Jerod Santo:** Awesome. We'll let you get back to your day... This is the end of my day, but the beginning of yours, so I'm sure you have some writing and some work ahead of you. I'll let you go. Thanks, Sean. |
**Sean Goedecke:** Thanks so much. |
• Amp is a coding agent that uses AI to modify code based on natural language instructions |
• Amp is multi-model, using multiple LLMs, and doesn't require users to select specific models |
• Cody is an older coding agent that is still used in the enterprise for non-agentic workflows |
• Gen AI phenomenon has led to a shift in technology, requiring a new approach for agentic models like Amp |
• The future of coding agents is seen as a force multiplier, but still requires delicate handling and understanding of their capabilities and limitations. |
• Model intelligence and limitations |
• User frustration and expectations vs. model capabilities |
• Drift in model performance and degradation in quality |
• Code review as a bottleneck in using AI tools |
• Strategies to address model quality issues, such as switching inference providers and using multiple model families |
• Recent report of quantized model rollout and impact on model quality |
• Importance of user intuition and skills in effectively using AI tools |
• Specific example of Claude Code losing functionality and requiring user input to correct it. |
• Amp operates similarly to other agents, using a for loop wrapping an agentic LLM |
• The loop takes user input, feeds it into the model, and generates a response, including tool calls |
• Tool calls are executed, and responses are fed back into the loop until complete |
• Sub-agents are specialized tools that perform targeted tasks within the agent |
• The client-server architecture allows for server-bound models and syncing of agentic interactions (threads) to the server |
• Threads are like transcripts of interactions, including user questions, tool calls, and results |
• The server-side store enables team-wide views of how others are using the tool and sharing of best practices |
• Amp can be installed via npm and has a CLI architecture inspired by NeoFetch |
• Discussion of command line tools and the challenge of making them visually appealing |
• Introduction of a new terminal UI framework built in-house for Amp |
• Elimination of flicker in the terminal UI and special shout-out to Tim Culverhouse |
• Importance of history and context in coding conversations |
• User experience and interactions with coding agents, including the concept of "Agent Flow" and "Document-Driven Development" |
• Standardization of context and behavior for coding agents through the use of agents.md files |
• Personal approaches to coding and user experience, including the use of roles and prompts to guide agent behavior |
• Development process for a project enhancement proposal (PEP) system to formalize project ideas and decisions |
• Importance of clear direction and guidance for a project, and how to provide it using a PEP system |
• Distinction between two types of development workflows: one where a clear plan is generated, and another where the workflow is more exploratory and iterative |
• Use of PEPs to document project ideas, decisions, and learnings, and to facilitate team collaboration and knowledge sharing |
• Borrowing of Python's PEP system and status tracking to organize and manage PEPs |
• Importance of having a structured process for documenting and reviewing project ideas and decisions. |
• The speaker, Adam Stacoviak, discusses his use case for Amp, a tool that allows him to work on long-running tasks while multitasking |
• He mentions his agent flow, which involves using a model to generate code and logs, and storing them in a repository |
• The logs serve as an audit trail, providing context for reviewing code and understanding the high-level intention behind it |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.