tweetindex
ID

Amp

@AmpCode · amp-devs@ampcode.com · joined 15 Mar 2025

Amp is the coding agent and development environment that runs anywhere and everywhere.

26 277Followers
64Following
334Posts total
1.2MViews on collected posts

Postingan terbaru

@sqs and @thorsten on the decay of the local dev env: "We found this with the shift to orbs, when as soon as you started making the Orb environment good, that's all people ever wanted to use." https://t.co/PlPXIXRwup
1:15
2.6K views · 8 likes · 0 reposts · 2 replies Open on X →
@sqs on the advantage of using a single coding agent across the whole org: "All of our intent, all of our history, is in Amp, in threads, in something that's legible to the agent." "You can see why this was added here, and you don't just get the commit message, you also get htt
1:26
6.5K views · 39 likes · 2 reposts · 2 replies Open on X →
"I'm just pointing at things and saying, make it like this and ship this and do this. The altitude is so high. It's wild. Even compared to two months ago." @thorstenball on using agents for the whole lifecycle of a feature: building, testing, shipping, monitoring the rollout, ht
1:43
36.7K views · 41 likes · 4 reposts · 7 replies Open on X →
What is the computer for now? In Raising an Agent S2E4, @sqs and @thorstenball explore how agents can do more than just ship code, discuss recent outages, and ask what happens to our computers when more work moves into Orbs. 00:00 Intro: What is the computer for now? 01:32 New
53:17
130.9K views · 63 likes · 7 reposts · 6 replies Open on X →
"I could just replace that with EC2 and some shell scripts and get the same thing." But could you? Thoughts and question of when to build and when to buy. And @sqs putting @thorstenball fully on the spot by asking him whether people should build their own Amp or not. https://t
2:09
7.1K views · 35 likes · 5 reposts · 4 replies Open on X →
@thorstenball's pet theory on why engineers are so busy tweaking skills and tools and workflows: "Because it can't be that easy, right?" https://t.co/CrM4gUEfW4
1:58
8.8K views · 43 likes · 4 reposts · 5 replies Open on X →
@AmpCode https://t.co/xGvzbUkpmi
GIF
5 views · 0 likes · 0 reposts · 0 replies Open on X →
@AmpCode still waiting on Amp swag to drop, I need to signal to my fellow ai-pilled-devs-in-hiding here in the suburbs that I know what I'm doing 55 views · 1 likes · 0 reposts · 1 replies Open on X →
@AmpCode I like how almost everyone is building with the mindset of "let's build more of what users already like, but better", while you guys build "let's build something good enough and then spend most of our time left building things people *will* use in a near future". 62 views · 1 likes · 0 reposts · 0 replies Open on X →
Quinn on everyone now building developer tooling: "Just building software to do X is only valuable if you can get people to pay and I think that's going to be a lot harder." https://t.co/nu9RSfaY7W
0:51
406.5K views · 44 likes · 1 reposts · 6 replies Open on X →
We're investigating an infrastructure failure that causes large parts of https://t.co/8Zxb4mjEcy being unavailable. Sorry about that. We'll keep you updated on https://t.co/5nxhNhfyhr. 9.7K views · 92 likes · 2 reposts · 15 replies Open on X →
@AmpCode @sqs @thorstenball when ability to develop iOS apps? 88 views · 0 likes · 0 reposts · 0 replies Open on X →
You can also watch it on YouTube: https://t.co/fDrBLqsdAh Or listen to it on Spotify: https://t.co/hC6cKMau4r If you want to listen to all of them: https://t.co/NxaedG7D6o 5.3K views · 6 likes · 0 reposts · 0 replies Open on X →
Raising an Agent, S2E3: When Tokens Flow Like Electricity. @sqs and @thorstenball on what happens when intelligence gets cheap: build vs. buy flips, why everyone building software to build software to do X is probably incorrect, and when software starts to feel like owning a htt
48:01
593.4K views · 58 likes · 8 reposts · 5 replies Open on X →

Dibandingkan akun berukuran sama

14 postingan dari 90 hari terakhir, dibandingkan dengan rentang 10K–100K pengikut. tampil luas, tetapi sedikit penonton yang merespons.

Median tayangan6 824akun ini924median untuk 10K–100K
Jangkauan, %25.97%akun ini3.62%median untuk 10K–100K
Interaksi, %0.26%akun ini1.52%median untuk 10K–100K
MetrikAkun iniMedian untuk 10K–100KRasio
Median tayangan per postingan6 8249247.39×
Jangkauan (tayangan ÷ pengikut)25.97%3.62%7.17×
Tingkat interaksi0.26%1.52%0.17×

Akun lain pada rentang ini →   Bandingkan dengan akun lain →   Bagaimana tolok ukur ini disusun →

Growth & engagement

How the posts we collected actually performed: views and reaction rate post by post, what the audience did with them, and where the follower count goes.

Views per post

593.4K27 Aug
5.3K
88
9.7K1 Sep
406.5K2 Sep
62
55
53 Sep
8.8K5 Sep
7.1K6 Sep
130.9K11 Sep
36.7K12 Sep
6.5K14 Sep
2.6K17 Sep

Last 14 collected posts, oldest on the left. The scale is logarithmic: one post can outrun the rest a hundred times over.

Engagement rate per post

0.01%27 Aug
0.11%
0.00%
1.13%1 Sep
0.01%2 Sep
1.61%
3.64%
0.00%3 Sep
0.59%5 Sep
0.63%6 Sep
0.06%11 Sep
0.15%12 Sep
0.66%14 Sep
0.38%17 Sep

Reactions — likes, reposts, replies and quotes — divided by views. Median for 10K–100K accounts is 1.52%.

What the audience does

Likes65.1%431 in total
Reposts5.0%33 in total
Replies8.0%53 in total
Quotes1.1%7 in total
Bookmarks20.8%138 in total

Share of every reaction we collected for this account. Replies mean argument, reposts mean endorsement, bookmarks mean the post was worth keeping.

The follower curve appears once this account has two daily snapshots — we take one a day, and this one is on its first.

Akun serupa

Frequently asked questions about @AmpCode

How many followers does @AmpCode have?

26 277 followers.

How many posts has @AmpCode published?

334 posts.

How do posts by @AmpCode perform?

Collected posts: 14. Views: 1 207 785. Likes: 431.