Практика Shadowing: The future of work with @Claude - Изучайте разговорный английский по видео

Выберите режим практики

Каждый режим открывает полноэкранную комнату практики.

120 предложений

Если предложения слишком короткие или длинные, нажмите Edit, чтобы их изменить.

What do you do if there's no Claude in the channel?

I don't know, I can't remember a world without Claude in the channel.

Walk me back.

Three years ago, we were just starting to adopt AI into our day-to-day workflows.

What was it like back then?

And take me all the way to where we are today.

I remember two years ago, I was still using typeahead.

That was what AI could do as an engineer.

And you know, we built Claude Code, we brought agents, and kind of the next generation of ways to do your coding.

And it’s just changed so much since.

With typeahead, I was still deciding, I want to write this line of code, and the agent was helping a little bit.

It was just writing the line.

And then we got to the point where it was writing whole functions, whole files, whole features.

And I feel like now with Tag, it just does the whole thing.

It can write the feature, it can do an entire experiment end-to-end, it does my data analyses.

It's been like two leaps in 2 years.

When I think back to the last couple of years, it's almost like this transition.

We went from a person always in the loop, it's one person sitting there, and they're just typing a line at a time.

We got to one person sitting there with like 10 Claudes, you know, typing a bunch of features at a time.

Now we're at the point where Claude is actually driving a little bit more.

And it's not just one person anymore, it's an entire team that's interacting with it.

So, what is Claude Tag?

In the past, you had to open Claude, and you had to ask it something, and then Claude would do the work.

It'll use your tools, it'll use your computer, and it'll get the task done.

That's the way that it used to be.

With Claude Tag, Claude jumps in, it's proactive, it knows when to jump in.

It'll do the work, even if it takes days or weeks, and it'll follow up.

And I think the coolest thing is, it'll remember what I told it for next time.

Before, I would have to prompt Claude every time, and I would have to say, "Claude, now do this, or now do this." I would have to remember to do that.

Now we just add Claude to a channel, it will proactively jump in and do the work.

Everyone gets to see it, everyone gets to participate, because it's multi-player, and it'll remember for next time.

Okay, so what on the research side actually enabled this?

How is it that Tag is so good?

For many years, we've been working on making our models more long-running and autonomous.

So if you look at the latest METR evals, our latest models can work for 16 hours at a time, and are now in the zone where we can't even accurately detect how long it's able to work for.

In something like Claude Tag, Claude is able to self-schedule work for itself.

And so you can take this one 16-hour task, and it actually increases over time because Claude can schedule a follow-up after days, or weeks, or months.

I feel like the task that we couldn't trust it to do before, now it can get almost every single time.

I have a bunch of these Claude Tag sessions, personally, that are running for days, weeks.

I think I might have one that's a month.

It's essentially this long-running experiment, and it's just checking in every day, checks the data, once in a while, it sends a bug fix if there's a bug that needs to get fixed.

I just see the pull requests coming in, and I get these data readouts every day.

The other big innovation is just being able to have memory in the model.

The model can not only set reminders for itself, but it can also remember just all the instructions that all the users have given it over time.

Memory took a long time to crack.

I think we tried to get it right for Claude Code for years, and it feels like we finally got it right. It feels really good to use.

If you're working with Claude Tag in a channel, and you tell it, "Hey, I want you to monitor only for this type of issue, but not these other categories," it will do that.

It will remember that for that channel forever after.

And then, if someone else says, "Hey actually, let me expand your scope to this new thing," it will adjust.

Another big thing that people love is Claude's personality and EQ.

Sometimes when I talk with people about adding Claude Tag into a channel, they say, "Oh, how do I know it won't jump in on every thread and be annoying?" Well, Claude is trained to have a good sense for when it's needed, and it can take the back seat.

If it ever goes too much in the wrong direction, you can just tell it to do something different, to jump in less, or jump in more, and it'll just remember it for the future.

So when you look at the internal usage, and when you talk with our customers who are getting started on Claude Tag, what are the patterns that you see?

The coolest thing to me has been how customers are figuring it out.

It can write your pull requests, it can debug production issues, it can do data analysis.

All you have to do is hook it up to your tools.

I think that's only possible because the memory is just so good.

And I've seen people do this emergent stuff where, you know, for example, this is a channel for Q&A, anytime a question is answered, you must check it off.

You tell Claude Tag this, and it'll just do that.

It'll answer the questions, and it'll react with a check every time, and it'll just do this for you.

We have a channel for data questions, and now Tag just answers all the questions.

Or we have the channel for Claude Code feedback, and Tag just fixes everything now.

The most common way that I ask a data question is, I post in our data channel, but then I tag Claude Tag, and then it takes the first pass, and normally it's pretty good.

I kept doing this in a bunch of channels, and then I just got tired of tagging it, so I just told it, "Please respond every time." I think it goes to show how powerful the memory is, that you're able to do something like this.

You can just tell it, "Hey, remember to always do this thing," and it just has your back.

It's been a huge shift in how we all do work.

I think this also is a way for more people to understand how to work with AI.

Because Claude Tag is working in public channels, everyone is able to observe how the expert users leverage it.

And then they take those patterns, and they bring it to new projects that they're working in.

And so both internally and in the customers that we've been working with, we've been seeing this diffusion of Claude Tag best practices that is, I think, very novel to AI tools.

It was surprising how fast it took over.

I feel like now I see Tag in every channel that we have; every feedback channel, every data channel.

It started with a few people using it, but I think as other people saw those people using it, they quickly picked it up.

It's been very empowering to be able to have Claude Tag have my back.

So for a lot of our existing tools, like Chat, Cowork, and Claude Code, you typically have to remember to open it.

And so it’s a more reactive experience.

And one thing that's great about Claude Tag is you give it this higher-level objective, like put up PRs for every bug in this channel, and it just has your back and puts up a PR for every single one without you needing to remind it.

The second thing that's really cool is that it's multi-player.

So almost all of the AI tools that people use right now are just you and Claude working together, and then copy and pasting this output to your team.

And I think the big shift that Claude Tag allows is, it brings Claude right into the middle of your work so that multiple people can guide the session to a better output.

There's so many, like, dynamics here.

Like one, we're all learning about how to use Claude Tag better by observing other people.

Claude Tag is learning how to better work with us by hearing the guidance that we're giving it.

At the end of the day, the customer gets a better result, because it's not just my opinion of how we should solve it, it's our whole team is able to jump in to nudge this PR to the best possible state.

I mean, I love this idea.

I keep telling everyone, I want everyone to contribute to the code base, and so many people are afraid because they have to, like, open a terminal, even the desktop app, because you have to deal with a Git and code checkouts and stuff.

And with Tag, they can just do it. It's really cool.

The other thing that I think is really important is making sure that your collaboration platform has public channels.

That way, Claude Tag can monitor different projects that you're tracking.

So as a PM, I'm often working on maybe five to 10 features, and I have Claude Tag look at the status for every single one, and then give me a daily report.

The other big unlock we've been seeing is that, people can now self-serve their questions.

When people onboard to our company, instead of asking Legal about whether they can say this, or instead of asking our HR team what our benefits are, they can just tag Claude Tag.

And because Claude Tag is connected with our source-of-truth files, it can give them a really fast answer, no matter what time they're looking for it.

I think the single biggest thing is just how much more productive it's made everyone.

And, you know, this is driven by our internal version of Claude Tag.

And if you look at just the product org, so, the part of the company that we sit in, the number of PRs that are written by Tag, I think it's like 65% now, and it's just climbing like this.

I thought that Claude Code was the thing that makes engineers go faster.

This is a product that makes engineers go way faster.

I think actually, a lot of the reason is, because the way you're interacting with it, you ask Tag to do something, and it'll respond, and you move on to the next task.

100

So you actually want to set it up in a way where Tag can do the work, and you don't have to check in all the time.

101

You have hundreds of these Claude Tags running, but you're still a power user of Claude Code.

102

How do you decide when to reach for each of them?

103

Yeah, so I used to use Claude Code for everything, and then I started using Tag for more and more things.

104

First, it was really simple fixes.

105

Someone has a bug, the button's off by a few pixels or something.

106

I'll just ask Claude, "Please fix it." Or someone has a simple data question, I'll ask them to fix it.

107

And I think what's been happening more and more over the last few weeks as I've been getting more comfortable with the product, is I've been using Tag for just more and more things.

108

And even more complicated work, it's actually able to do.

109

Because it can verify its work, because it's running in the same remote sandbox that we use for mobile and for the desktop app, and it's using the same agent SDK.

110

So it's just as intelligent.

111

When you add memory to this, in different channels, I have specific preferences about how I want it to verify.

112

It might be a little bit different for every channel.

113

Often what it does is it'll fix some bug, then it'll post back a video in Slack, and I don't even have to leave it.

114

What's next for Claude Tag?

115

So we launched Claude Tag in Slack, and we're excited to bring it to more platforms where people collaborate, like Microsoft Teams.

116

We want to make sure that every knowledge worker is within arm's length of Claude, no matter where they're getting their work done.

117

And I think one of the coolest parts of Claude Tag is, it's not just changing how individuals work, it's putting Claude in the center of teams and transforming entire orgs.

118

We've built Claude Tag to be incredibly customizable, just like Claude Code.

119

And I'm so excited to see how orgs customize Claude Tag and make it their own.

120

I can't wait.

Скачать приложение

Всё для свободной речи

ИИ-оценка произношенияОценка каждой фразы

Практика IPAОсвойте каждый звук

СловарьСоберите свой словарный запас

Игра со словамиУчитесь играя

Сканировать QR

Download on theApp Store Get it onGoogle Play

Тот же канал

Building the best agentic analytics harness: Powered by Claude, built with Claude Code

Business EnglishUniversity StudentsWorking Adults

Building the future of agentic infrastructure

Business EnglishUniversity StudentsWorking Adults

FOR YOU

Об этой уроке

На этом уроке вы будете практиковать разговорный английский, основываясь на интересной беседе о будущем работы и внедрении ИИ в повседневные задачи. Мы сосредоточимся на развитии навыков shadowspeak, что позволит вам более свободно и уверенно общаться на английском языке. Вы узнаете о применении технологий, о том, как работать в команде и как ИИ может облегчить рабочие процессы.

Ключевая лексика и фразы

Прокативаться (to jump in) - активно включаться в процесс.
Автономный (autonomous) - способный действовать самостоятельно.
Напоминание (reminder) - функция, позволяющая запомнить важные задачи.
Чекать данные (to check in) - периодически проверять информацию.
Функции (features) - возможности, которые предлагает программа или устройство.
Собирать результаты (to send a data readout) - предоставлять отчет о состоянии работы.
Многопользовательский (multi-player) - возможность совместного взаимодействия несколькими пользователями.
Совместное взаимодействие (collaborative interaction) - работа в команде над одной задачей.

Советы по практике

При использовании видео для shadow speech важно внимательно следить за интонацией и ритмом говорящего. Видео имеет умеренный темп, что делает его идеальным для практики разговорного английского. Попробуйте следовать за спикером, повторяя за ним фразы сразу после того, как он их произнесет. Это поможет вам улучшить произношение и беглость. Также обратите внимание на использование пауз - они часто показывают, когда спикер хочет подчеркнуть какую-то мысль, и их копирование сделает вашу речь более естественной. Если вы столкнетесь с сложными словами или фразами, не бойтесь останавливать видео и повторять их несколько раз подряд, чтобы закрепить навык. Регулярное использование техники shadowspeaks значительно повысит ваше доверие к разговорному английскому и улучшит понимание тем разговора.

Грамматика в этом видео

Конструкции, которые говорящий использует чаще всего, с точными словами из видео:

Конструкция	В видео
Present Perfect Continuous have/has been + -ing — действие началось раньше и продолжается	we've been working · we've been seeing · what's been happening
Present Perfect have/has + причастие прошедшего времени — прошлое действие, важное сейчас	It's been · have given · has been
Пассивный залог be + причастие прошедшего времени — важно, что происходит, а не кто это делает	is trained · is answered · is connected

Что такое техника Shadowing?

Shadowing — это научно обоснованная техника изучения языка, изначально разработанная для подготовки профессиональных переводчиков и популяризированная полиглотом доктором Александром Аргуэльесом. Метод прост, но эффективен: вы слушаете аудио на английском от носителей языка и немедленно повторяете вслух — как тень, следующая за говорящим с задержкой в 1–2 секунды. В отличие от пассивного прослушивания или грамматических упражнений, Shadowing заставляет мозг и мышцы рта одновременно обрабатывать и воспроизводить реальные речевые паттерны. Исследования показывают, что это значительно улучшает точность произношения, интонацию, ритм, связную речь, понимание на слух и беглость речи — что делает его одним из самых эффективных методов для подготовки к IELTS Speaking и реального общения на английском.

Техника шедоуинга: читать полное пошаговое руководство →

Практика Shadowing: The future of work with @Claude - Изучайте разговорный английский по видео

Выберите режим практики

Скачать приложение

Тот же канал

Build a proactive agent workflow with Claude Code

Tag Claude in, right where you already work

Build data-driven lesson plans with Claude for Teachers

Can you trust what AI tells you?

How AI gets its character

Plan smarter with Claude for Teachers

How Claude Code Works

Building the best agentic analytics harness: Powered by Claude, built with Claude Code

Building the future of agentic infrastructure

Рекомендуемое видео

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

Communicating the Future: Defining Where We Want AI To Take Us

Translating Claude’s thoughts into language

A Day in the Life of an Amazon Software Engineer

/wayfinder: Nothing is too big to plan anymore

Did someone say... SecondBrain?

OpenAI’s new browser feels familiar…

Cloud Providers are changing RAPIDLY [REUPLOAD]

Codex Is Winning… So Why Am I Still Paying for Claude?

Learn 95% of ChatGPT Work in Under 20 Minutes

Об этой уроке

Ключевая лексика и фразы

Советы по практике

Грамматика в этом видео

Что такое техника Shadowing?