
growth @encoredotdev • agent-first aws/gcp automation • 2x YC
Austria / Croatia
Joined August 2017
- Tweets1.4K
- Following360
- Followers1.5K
- Likes2.2K
if i recall correctly, when @linear launched in 2019 i kept seeing a lot of push back on the adoption of it because a lot of people didn't want to give up their jira habits, even though the opinionated way was just more productive.
luckily, agents are able to just pick the better tool on day one instead of wrestling with years of "but this is how we've always done it"
nothing better than @linear for agents.
even new ones like Grok Bot just native grok how to use it. Simple, well-defined primitives and workflows. No custom databases, pages, or novel-length skill files.
PaaS is a phase, nearly every team i've watched start on one over the years ends up back in their own aws or gcp account
having a customer for two decades is going to get so much rarer in dev tools, since switching used to cost a team a quarter and now it's an agent and an afternoon
the only lock-in left is people liking you
(funny when you think about it, marketing never really changes)
building tools for myself has been the most fun part of my year, but the moment a few people asked to use them was where most of them would've died.
going from "runs on my laptop" to "lives somewhere other people can open it" is the first real friction point now, it's doable but it's exactly where most people give up.
coincidentally, that's the part i'd love agents to make boring.
every bit of friction you ship now is someone (or some agent) quietly picking something else, and nobody's immune to that, not even the company everyone used as the DevEx example
It is so sad to see how bad @twilio developer experience has become over the past year.
There was a time when twilio’s DevEx was a case study in how to build great developer tooling.
So many bugs, constant login cycle, broken access setups.
How’s the right person to talk to? Who can actually fix things and improve the experience?
People on X love talking about how devtools should handle user feedback, this thread is a good example of how to do it.
Props to @AmpCode
Sorry for these issues. =/ That sucks. Can you please report a bug (ampcode.com/docs/support/rep…) when you hit these? We fix stuff super fast, and the surface area here is so so big that it's really hard to diagnose stuff otherwise.
As for the confusing mode and model stuff, that is 97% on us and we are taking a chainsaw to that shit in Amp and will have a ton of improvements very soon.
And I am making it so you can disable Amp credits. However, then the question arises: what about dictation? What about Jev that's now sprinkled throughout? Etc. It's super hard to figure these things out, but we have the best users and tons of super helpful bug reports from all the variations and please keep 'em coming!
How are you letting coding agents touch your cloud accounts today?
Curious what people are actually doing in practice (scoped IAM roles, read-only, nothing at all?)
Here are some initial thoughts on trying @AmpCode.
TL;DR: Getting it to work with my ChatGPT sub was unnecessarily confusing (I assume most people will want to try Amp with what they have before buying Amp credits), but it started to feel worth it once I got past the onboarding hiccups.
I've been super happy with my vanilla Codex/Claude Code setup these past few months and have deliberately kept my sessions laptop-only (no remote tmux, etc.).
But for some reason, @AmpCode and their Orbs kept giving me a good vibe, so here we go.
Any tips?
The agent then checked my logs, verified my sub worked and got a response by pinning GPT-6.1 in a custom mode and changing my launcher (idk if it just picked a hack because I was impatient, but connecting a sub should involve less troubleshooting).
After that I let the agent set up a runner on my always-on Mac mini over SSH, so now I'm excited to get some real usage in with the Mac app as @sqs suggested and try self-hosted Orbs, but wanted to share these onboarding thoughts first! For anyone who made it this far, give Amp a go: ampcode.com











