50 Best Tweets About Coding (2026)

A curated collection of the sharpest, most-shared X posts about coding—saved so you do not have to dig through the timeline yourself. Updated weekly.

Developers on the bugs, the tools, and the takes that get the whole timeline arguing.

Creators
43
Updated

Top Coding tweets from 43 creators

Ranked 01–50

  1. 01

    @Jeremybtc ·

    Anthropic accidentally leaked their entire source code yesterday. What happened next is one of the most insane stories in tech history. > Anthropic pushed a software update for Claude Code at 4AM. > A debugging file was accidentally bundled inside it. > That file contained

    • 1.4K Replies
    • 8.5K Reposts
    • 52.7K Likes
    • 3.1M Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  2. 02

    @akshay_pachaar ·

    A single 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 file just hit 15K GitHub stars. (derived from Karpathy's coding rules) Andrej Karpathy observed that LLMs make the same predictable mistakes when writing code: over-engineering, ignoring existing patterns, and adding dependencies you never asked for. If

    • 94 Replies
    • 746 Reposts
    • 7.7K Likes
    • 726.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  3. 03

    @karpathy ·

    It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December

    • 1.6K Replies
    • 4.7K Reposts
    • 37K Likes
    • 5.2M Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  4. 04

    @techNmak ·

    Andrej Karpathy wrote something that every Claude Code user has felt but couldn't articulate. Three quotes. Read them slowly. "The models make wrong assumptions on your behalf and just run along with them without checking. They don't manage their confusion, don't seek

    • 52 Replies
    • 210 Reposts
    • 2.1K Likes
    • 184.3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  5. 05

    @naval ·

    Vibe Coding Is the New Product Management “There’s been a shift—a marked pronouncement in the last year and especially in the last few months—most pronounced by Claude Code, which is a specific model that has a coding engine in it, which is so good that I think now you have vibe

    Video thumbnail from Naval's post Watch video
    • 419 Replies
    • 689 Reposts
    • 6K Likes
    • 543.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  6. 06

    @heygurisingh ·

    Holy shit... Addy Osmani just dropped something that will make "Vibe Coders" loose their mind. It's called Agent Skills. Production-grade engineering workflows that force AI coding agents to actually behave like senior engineers, not interns shipping prototypes to prod. →

    • 43 Replies
    • 123 Reposts
    • 921 Likes
    • 76K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  7. 07

    @milan_milanovic ·

    𝗟𝗟𝗠𝘀 𝗔𝗿𝗲 𝗡𝗼𝘁 𝗥𝗲𝗮𝗱𝗶𝗻𝗴 𝗬𝗼𝘂𝗿 𝗖𝗼𝗱𝗲 We keep calling LLMs "AI coding assistants." But writing code and understanding code are not the same thing. Researchers from Virginia Tech and Carnegie Mellon University just ran 750,000 debugging experiments across 10 models to determine how well

    • 90 Replies
    • 258 Reposts
    • 1.2K Likes
    • 117.9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  8. 08

    @heygurisingh ·

    Vibe coders are not going to like this. UC San Diego just published the first real field study of experienced developers using AI agents. They watched 13 of them code in the wild and surveyed 99 more. Zero of them vibe coded. Not one developer "fully gave in to the vibes." Not

    • 351 Replies
    • 313 Reposts
    • 1.9K Likes
    • 279K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  9. 09

    @om_patel5 ·

    SENIOR ENGINEERS ARE QUIETLY SWITCHING FROM CLAUDE CODE TO CODEX AND HERE'S THE BRUTAL BREAKDOWN a 14-year principal engineer spent ~120 hours co-developing (not vibe coding) across both tools on an 80k LOC python/typescript project. here's what he found: Claude feels like an

    • 120 Replies
    • 117 Reposts
    • 1.2K Likes
    • 146.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  10. 10

    @om_patel5 ·

    a 58 year old guy just dropped the best take on vibe coding i've ever read. MD. PhD. triple board certified. been writing code since the 1970s. he said Claude Code is the biggest leap in programming he's seen in his entire career. and he's seen every single one. he said Claude

    • 85 Replies
    • 99 Reposts
    • 1.3K Likes
    • 129K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  11. 11

    @rauchg ·

    Code is an output. Nature is healing. For too long we treated code as input. We glorified it, hand-formatted it, prettified it, obsessed over it. We built sophisticated GUIs to write it in: IDEs. We syntax-highlit, tree-sat, mini-mapped the code. Keyboard triggers, inline

    • 288 Replies
    • 245 Reposts
    • 2.6K Likes
    • 316K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  12. 12

    @Suryanshti777 ·

    Claude Opus 4.7 didn’t just improve coding. It quietly killed the way most developers think about coding. But almost no one is using it the way Andrej Karpathy describes. People are still stuck in: “write this function” “fix this bug” “explain this code” That’s not wrong.

    • 21 Replies
    • 29 Reposts
    • 281 Likes
    • 50.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  13. 13

    @alex_prompter ·

    Some of the most starred repos on GitHub right now contain zero runtime code. They're markdown files, skill configs, and prompt collections that change how AI models behave. 6 repos worth knowing about, ordered by stars: 1. obra/superpowers (200K+ stars) A full development

    • 14 Replies
    • 43 Reposts
    • 226 Likes
    • 22.5K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  14. 14

    @neetcode1 ·

    Forgot to post on twitter - my conversation with @thdxr from @opencode Talked a lot about how programming is changing & not changing. I really enjoyed a lot of the historical takes that Dax has. He's building one of these "agentic coding" tools, so he sees the value in it, but

    Video thumbnail from NeetCode's post Watch video
    • 16 Replies
    • 19 Reposts
    • 569 Likes
    • 40.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  15. 15

    @jsmasterypro ·

    "AI ruined coding" is the hottest take in tech right now. But what exactly did it ruin? Writing the same CRUD endpoints for the 400th time? Debugging webpack configs? Copy-pasting from Stack Overflow? AI took away the parts I hated and left me with the parts I love:

    • 151 Replies
    • 66 Reposts
    • 858 Likes
    • 46.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  16. 16

    @gregisenberg ·

    a post called "the west forgot how to code" is going viral among devs. the thesis: AI assisted devs ship faster but understand nothing. the next generation will be illiterate at the layer that matters. tbh, this panic happens every single decade. - assembly devs said C devs

    • 114 Replies
    • 43 Reposts
    • 446 Likes
    • 40.5K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  17. 17

    @DavidOndrej1 ·

    how to ship a full app in weeks with AI. agentic engineering not vibe coding, built-in feedback loops, the exact stack, and what to steal from this episode: 1. michael writes 95% of his code with AI and he's an actual developer at convex. last 3 months, one big app, agentic

    Video thumbnail from David Ondrej's post Watch video
    • 17 Replies
    • 4 Reposts
    • 150 Likes
    • 7.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  18. 18

    @Hesamation ·

    today, I watched this DHH interview for a 2nd time. his approach to AI coding is much more playful and curious than many other experienced devs, and he’s very good at articulating why. some takeaways: “the best programmers are currently more valuable than ever because they’re

    • 1 Replies
    • 12 Reposts
    • 270 Likes
    • 21.1K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  19. 19

    @clairevo ·

    I have been coding for over 20 years (!!!) and I’m sitting here, mouth agape, watching codex: - planned full refactor of core app, published in a pretty html for my review and co-authorship - iterating through loops to code piece by piece, document and update architecture plans

    • 41 Replies
    • 15 Reposts
    • 344 Likes
    • 26.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  20. 20

    @rohanpaul_ai ·

    Chamath on how AI agents are making the "10x engineer" distinction disappear because the most efficient "code paths" are now obvious to everyone. Just as AI solved chess and removed the mystery of the best move, AI is doing the same for coding, making the process reductive and

    Video thumbnail from Rohan Paul's post Watch video
    • 145 Replies
    • 61 Reposts
    • 555 Likes
    • 242K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  21. 21

    @anulagarwal ·

    Greatest vibe-coding hack (step-by-step): >Code with Opus 4.6 (in Claude Code) >Ask Codex GPT 5.4 to review and make a detailed plan of any problem it finds, why they are a problem, and how they can be solved >Copy plan to Opus 4.6 and ask it to review >Ask Opus 4.6 to implement

    • 18 Replies
    • 9 Reposts
    • 109 Likes
    • 7.4K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  22. 22

    @LBacaj ·

    We’re making a fundamental tradeoff when we use these coding agents, but some of my engineering friends still don’t seem to get it. I see a lot of engineers make the argument “AI outputs still aren’t that great, code quality isn’t the same as writing it by hand.” And it’s all

    • 83 Replies
    • 38 Reposts
    • 473 Likes
    • 53.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  23. 23

    @carlhua ·

    i used to write flight software - you know, the one that flies jets and spacecrafts.. and if I had claude/codex back in the day, i wouldnt even need to look at code. hear me out, people say AI slop this, AI slop that, and the code it generated is trash etc etc. the thing is,

    • 81 Replies
    • 9 Reposts
    • 272 Likes
    • 46.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  24. 24

    @bibryam ·

    If you missed, check out my latest post 👇 →12 patterns behind production coding agents← 1. Persistent instructions: durable rules repo. Helps consistency. Trade-off: goes stale. 2. Scoped context: load rules by directory. Helps local accuracy. Trade-off: harder to debug. 3.

    • 4 Replies
    • 13 Reposts
    • 90 Likes
    • 5.1K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  25. 25

    @SergioRocks ·

    Software development tools changed more in 18 months than in the previous 10 years. From 2014 to 2024, the toolbox was stable. - Jira for planning - GitHub for code - VS Code for editing - CI/CD for shipping The improvements were incremental. Better linters. Faster pipelines.

    • 18 Replies
    • 20 Reposts
    • 158 Likes
    • 24.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  26. 26

    @zarazhangrui ·

    How my own usage of coding agents has changed in the past month: 1. Moved from the terminal to the Codex/Claude Code desktop apps. The Codex Mac app is especially great. Now I rarely open the terminal 2. Transitioned from mostly Claude Code to 50-50 Claude Code and Codex. Codex

    • 48 Replies
    • 17 Reposts
    • 279 Likes
    • 37.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  27. 27

    @milan_milanovic ·

    𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗺𝗮𝗻𝘂𝗮𝗹, 𝘃𝗶𝗯𝗲, 𝗮𝗻𝗱 𝗮𝗴𝗲𝗻𝘁𝗶𝗰 𝗰𝗼𝗱𝗶𝗻𝗴? A long time ago, we coded only manually, but then we started to vibe code. Yet, vibe code is something everyone defines differently. The question is, can we take the best from both worlds and make something more

    • 10 Replies
    • 22 Reposts
    • 104 Likes
    • 5.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  28. 28

    @smratitiwa86867 ·

    Developers are quietly building a second brain inside their AI coding tools right now. And almost nobody realizes how important this shift is. Claude Code’s "Skills.md" looks like “just another markdown file.” It’s not. It’s the beginning of programmable AI memory for

    • 5 Replies
    • 9 Reposts
    • 35 Likes
    • 1.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  29. 29

    @manthanguptaa ·

    This talk from @badlogicgames is such a wake up call and something I have been saying for a while. Slow the F down with this agentic vibe coding. We are already seeing the consequences. More breaking software than ever, constant instability in dev tools, and a noticeable spike

    • 8 Replies
    • 4 Reposts
    • 80 Likes
    • 4.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  30. 30

    @Suryanshti777 ·

    Most people use Claude Code like a smarter autocomplete. Senior engineers use it like an operating system. The real upgrade isn’t faster typing. It’s splitting software development into parallel AI workflows: → one agent researches → one plans architecture → one writes code →

    Video thumbnail from Suryansh Tiwari's post Watch video
    • 9 Replies
    • 10 Reposts
    • 54 Likes
    • 5K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  31. 31

    @Franc0Fernand0 ·

    I think vibe coding is great for experienced developers. It’s a way to turn out a lot of good code very quickly. An experienced developer can learn how to write prompts that get the job done and reduce the chance of mistakes. After that, they can carefully look over the code and

    • 30 Replies
    • 10 Reposts
    • 115 Likes
    • 9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  32. 32

    @smratitiwa86867 ·

    🚨 99% of developers are using AI completely wrong. They're asking AI to write code. Senior engineers are building entire software systems with it. The difference isn't the model. It's the workflow. Most developers: ❌ Jump straight into coding ❌ Ignore architecture ❌ Skip

    • 6 Replies
    • 7 Reposts
    • 29 Likes
    • 1.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  33. 33

    @andrewchen ·

    why are spreadsheets the GOAT of no code tools? - unintimidating interface, just type numbers in a grid - easy to make something useful - shareable with a link - copy and make your own - insanely deep use cases (as a database, CRM, forecasting tools, etc) - finance team loves it,

    • 25 Replies
    • 9 Reposts
    • 80 Likes
    • 13.5K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  34. 34

    @nurijanian ·

    PMs have been "vibe-coding" since the dawn of times, we just didn't call it that when AI writes your code, your job is managing code you can't fully read. isn't this what PMs used to do before? have any of you actually looked at the code your eng team wrote? there's this great

    • 1 Replies
    • 4 Reposts
    • 26 Likes
    • 3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  35. 35

    @Trader_XO ·

    I’ve been thinking about this a lot lately - Agentic Coding and framework choice. As someone who’s comfortable with TypeScript with Nest, C# with .Net Core, Python Fast API, and Go, when it comes to building a bunch of APIs, I’ve found myself pausing less to ask can I build this

    • 27 Replies
    • 10 Reposts
    • 193 Likes
    • 29.5K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  36. 36

    @asmah2107 ·

    Traditional coding: > good vs bad dev might be 5-10x productivity gap. Vibe coding: > good vs bad might be 100x. AI amplifies judgment, taste, and systems thinking - not just speed. Most people haven't realized this yet.

    • 18 Replies
    • 6 Reposts
    • 68 Likes
    • 3.3K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  37. 37

    @Hartdrawss ·

    Hot Take : Vibe coding will NOT replace developers. The argument is wrong. Here's exactly why. Vibe coding replaces the tedious parts — boilerplate, CRUD scaffolding, first drafts of UI, repetitive patterns. It does not replace: > Knowing what to build in the first place >

    • 19 Replies
    • 2 Reposts
    • 46 Likes
    • 6.1K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  38. 38

    @ibuildthecloud ·

    I started developing with coding agents outside of my fancy sandboxes I built, it's terrible. How do you people live like this. Barbarians. I've gotta show you how I do it, because the "sandboxes" that coding agents provide are complete crap. Like Codex/Claude Desktop, crap.

    • 23 Replies
    • 2 Reposts
    • 100 Likes
    • 13.7K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  39. 39

    @nurijanian ·

    Saw the Claude Code vs Cowork debate on r/PM. Here's the framework I'd actually use: 1. Cowork wins for one-off work. Writing a doc, quick research, visualizing a decision you won't revisit. It's faster if you're not building something that needs to persist. 2. Cowork also

    • 2 Replies
    • 4 Reposts
    • 13 Likes
    • 1.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  40. 40

    @AlexEngineerAI ·

    the people warning about vibe coding are the same ones who said: "no IDE, real devs use vim" "learn CS before any framework" "get a degree before building" every tool that lowers the barrier gets this. messy code that ships beats clean code that never launches.

    • 20 Replies
    • 0 Reposts
    • 19 Likes
    • 1K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  41. 41

    @Layton_Gott ·

    Being a good developer can actually make you worse with coding agents at first. Because you treat the agent like a worse version of yourself. You expect it to infer the obvious You interrupt too early You patch things manually before the loop finishes You give it “just fix

    • 7 Replies
    • 0 Reposts
    • 21 Likes
    • 522 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  42. 42

    @ujjwalscript ·

    The "AI makes you a 10x Developer" you keep seeing on X is an ABSOLUTE illusion. And the empirical data finally proves it! The overwhelming consensus right now is that AI coding tools make every developer 10x faster, rendering foundational learning obsolete. Here is what the

    • 6 Replies
    • 5 Reposts
    • 19 Likes
    • 2.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  43. 43

    @hugobowne ·

    "For decades I was all in on Python. Now I don't care. TypeScript, Go, Rust, whatever. Verification isn't about looking at the code, it's whether it actually does what it needs to do." -- @intellectronica (ex-Google, ex-Microsoft, now at Jimini Health) Yesterday I spent 3.5

    Video thumbnail from Hugo Bowne-Anderson's post Watch video
    • 0 Replies
    • 1 Reposts
    • 15 Likes
    • 2.2K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  44. 44

    @AllurePixel ·

    Collins named "vibe coding" Word of the Year I've been doing it for 1 months with zero coding background Here's what nobody tells you 41% of all code written in 2026 is AI-generated MIT called it a top 10 breakthrough technology 63% of vibe coding users are non-developers

    • 6 Replies
    • 0 Reposts
    • 11 Likes
    • 113 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  45. 45

    @pascal_bornet ·

    Being a developer in 2026 may look like scrolling your phone while AI writes the code. But that is not the real job. The real job is knowing whether the code should exist at all. This is the funny part of the AI coding era: AI can generate nonstop. Functions. Tests. Docs.

    Video thumbnail from Pascal Bornet's post Watch video
    • 5 Replies
    • 9 Reposts
    • 36 Likes
    • 4.9K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  46. 46

    @ttunguz ·

    The $20/Month Software Revolution Software development has operated within established boundaries for decades, with clear divisions between those who code & those who don’t. But what happens when those boundaries dissolve overnight, & anyone can build functional applications

    Video thumbnail from Tomasz Tunguz's post Watch video
    • 3 Replies
    • 1 Reposts
    • 9 Likes
    • 2.8K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  47. 47

    @staysaasy ·

    Coding tools are now like gun collecting. > I got Cursor with VcCode completions and thirteen agentic agents in the background on separate work trees. I use codex when it’s a precise problem and Haiku on a loop for my rasberry pi. I alternate Opus 4.6 and ChaGPT 5.4 through

    • 3 Replies
    • 0 Reposts
    • 12 Likes
    • 691 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  48. 48

    @anulagarwal ·

    i uninstalled all IDEs/code editors from my system earlier this year. not because i became a better developer. because the models and agentic coding tools became too good i don’t really read the code anymore -> i just prompt, wait, test, complain, iterate. this works for almost

    • 2 Replies
    • 0 Reposts
    • 12 Likes
    • 987 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  49. 49

    @heavybit ·

    AI coding tools are getting better fast, but what happens to software engineering when abstraction becomes more important than implementation? Joe Ruscio (@josephruscio) talks with Steve Krouse (@stevekrouse) of @ValDotTown about developer tools, coding agents, and the future of

    Video thumbnail from Heavybit's post Watch video
    • 0 Replies
    • 2 Reposts
    • 1 Likes
    • 92 Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.
  50. 50

    @ThePracticalDev ·

    Early coding languages were tied to one target and platform. This dev traces how Scala, Kotlin, and Rust broadened their reach over time. { author: @nicolas_frankel } https://t.co/5OD4qVUgIJ

    • 0 Replies
    • 1 Reposts
    • 4 Likes
    • 2.5K Views
    View on X
    Rewrite this post in your own voice and angle. See the hook, structure, and reusable template behind this post.

Explore more of the best tweets on X.

Browse all tweet collections

Tweet Remixer

Remix this post

Creator

@creator

View on X

Choose a tone