Travis Lyons

This is React2Shell monitoring with Code Insights across 512 repos, totaling 17GB and 42M lines of public code. @trly_dev shows how it's done.

Excited to be presenting CI/CD pipeline triage with coding agents at Lansing Codes next week. If you're in the area, be sure to come check it out! Link in thread

my daughter typed this and told me I can't delete it, so I guess I need to commit it. good thing I taught her line comment syntax.

🆕 Building the God Coding Agent youtu.be/b4rOVZWLW6E @AmpCode has been popping up all over the timeline. @sqs and @thorstenball joined the pod to discuss: - IDE extension vs TUI for coding agents - How they ship 15x/day - Why subagents are overrated - The diminishing importance of model selectors - The evolution of the SDLC And many more hot takes on the state of AI coding adoption 👀

Just passed 400 members in Build Crew! If you want to join a community of devs building with agents, come on over. buildcrew.team (If you use Amp, we also give you $100 credit as well.)

This is correct. We had this same reaction in the 1980s & 1990s when compilers generated assembly for us. We hated it. Looking at the generated code made us puke. It got better.

Going live to launch Build Crew in 2 hours! If you're building with agents, you're going to learn a lot by joining this community. Everyone is welcome, no matter what agent you use. Little bonus: If you use Amp and join Build Crew, we'll pop $100 credit into your account so you can crank out more code.

I've been using up to a dozen coding agents at a time for nearly a week straight. Just added my 13th. All working on the same project. It worked amazingly up to about 200k LOC, and now they've begun savagely overwriting each other's work rather than try to deal with merge conflicts. Every few hours I have to shut them all down, fix a trainwreck, and bring them up one by one. But I've written a quarter million lines of heavily reviewed, heavily tested, carefully architected code in right around six days, ever since I got a very particular bug up my ass. 250k lines of real code, enterprise grade, in a week. This is the way to do it. I'm using @AmpCode, and I'm building a surprise. Stay tuned.

Sun: shining Beers: drinking @AmpCode: clanking It was a good day

Ask for a mock-up and get rickrolled 😂 Create a new storybook that will display an individual learning guide, create the following components, along with respective storybooks for each component: - table of contents - guide header - an optional overview section that can include a video file - the actual guide content, just include a placeholder for now I can't remember the last time I had this much fun building new stuff. Thanks @AmpCode

@Siddharth87 @AmpCode @thorstenball Love the guide, especially the touch point on Toolboxes! How’s your experience using them?

Loving the new TUI by @AmpCode I tried out Amp for the first time a few months ago but then defaulted to Claude Code. However, CC hasn't been behaving well recently so I decided to give Amp a real shot, and it's great. Wrote a quickstart guide on it if you're looking for a new coding agent - siddharthbharath.com/amp-code-guide/

My favorite part about @AmpCode is that you can share your whole session globally. PRs with Amp threads attached make me very, very happy as a maintainer. here is one from a bug fix this morning: ampcode.com/threads/T-24dc…

Amp now lets you provide tools to the agent with a few lines of code. Instead of writing an MCP server, you can drop any executable into a directory you tell Amp about. As long as the executable can produce a tool description, Amp will pick it up. This way Amp doesn't have to guess how to perform a task, but will get it right basically every time. Watch it prefer a purpose-made tool to using Bash for running the tests:

@thorstenball My go-to is just lazyvim.org/installation and then get work done.

Roast my .vimrc! I haven't changed it in 1.5yrs. Now I see that a lot has changed in Neovim land and I want to know what I'm missing out on. What should I try out, chuck out, replace?

Amp CLI can now read diagnostics from JetBrains IDEs for JVM languages such as Java, Kotlin, and Scala. ampcode.com/news/jetbrains…

Today we followed through on a commitment made on May 17: @AmpCode would switch to AGENTS not AGENT dot md if OpenAI could get the domain. They did, and now Amp and several other tools have aligned on a standard agent filename. Huge thanks to OpenAI and all the other agentmakers!

Get ready for Next Token! New live show every Wednesday hosted by me and @thorstenball. Launching Sep 3rd. Guests already confirmed: @dhh @mckaywrigley If you're an engineer using agents, you won't want to miss it. @theo and @ThePrimeagen - want to hop on the show sometime?

New live show Next Token with @ryancarson and @thorstenball, with first guests @dhh and @mckaywrigley. Self-recommending.