Tim Lucas
@toolmantim
Venn diagram of sandwiches, climbing, design and programming. Design @ampcode. Prev: co-founder @buildkite, and other stuff too. ❤️ @canarycarla
Our next step towards more agents in the terminal: amp -x
In this episode, Beyang and Thorsten discuss strategies for effective agentic coding, including the 101 of how it's different from coding with chat LLMs, the key constraint of the context window, how and where subagents can help, and the new oracle subagent which combines…
Good to see @Sonos has addressed their quality issues 😬 They still have a chance to save customers that haven’t switched their audio gear… yet (like me)
does anyone here use amp code? if you work at sourcegraph you are not allowed to comment
This is the way. ampcode.com/manual#princip…
Harsher reality: The sooner our tools pick the appropriate model for each prompt the better. This pattern to make users pick an AI model expecting us keep up with all of the nuances or names is untenable. Developers may like to tinker but the rest of us would rather not.
the new design process is no set process. @jenny_wen completely nails it. 🗒️jennywen.ca/notes/dont-tru…
Why can’t @rsms just produce every font on the planet? I’ve resorted to using fonttools to modify fonts w/ @AmpCode, having it create and compare spec sheets using Inter as the gold standard.
We just opened a design engineer position on @AmpCode! ampcode.com/hiring/design-…
Never, not in a million years, would I have believed you if you had told me: "Someone's going to read your marketing copy live, on air, on a podcast"
🎉 New episode with @thorstenball! Thorsten returned to @Sourcegraph to work on @Amp because he believes being able to talk to an alien intelligence that edits your code changes everything. On this episode, Thorsten joins us to discuss: 🤖 Exactly how coding agents work 🧰…
V similar changes: - Asking to investigate and provide options - Iterating prompts based on how the thread progressed - Recently: asking it to clone a dep’s git repo and investigate an API or concept (helps it, helps me, and only usually takes < 1min… it figures out the URL)
Fascinating to look back at my first Amp threads and see how my own usage has changed 1,221 threads (and a few months) later. - Longer, more detailed initial messages, shorter followups - Better context/prompts in my initial msgs to eliminate ambiguity/avoid pitfalls
I love a good GUI, but my use of homebrew-installed CLI tools has gone way up w/ @AmpCode. Last time it was for tweaking fonts… this time for video. ampcode.com/threads/T-e63c…
Look! A new Amp homepage! Fantastic job by @toolmantim. I love it.
Being able to quickly whip up a custom tool, right where you're working, is such a design super power. I gave zero UI/aesthetic/syntax direction to @AmpCode, only focused on what I needed to move forward. And I'll just `rm` it all when I'm done.
