Shadowing Practice: I Tested The Viral Reverse Engineering Repo - Learn English Speaking with Video

בחר מצב תרגול

כל מצב פותח חדר תרגול במסך מלא.

182 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
I want you to look at these two apps on my screen.
2
Now, one of them is a real production application called MongoDB Compass, which is built by MongoDB, is open source and is pretty popular.
3
Now, another one was a clone of this that I built with AI in 30 minutes and cost me $13.
4
Now, I built this clone using reverse engineering anything, which I'm going to talk about in this video, but right now, honestly, try to guess.
5
You can see one app on the side here.
6
I can click into different database fields, right?
7
I can see all the different entries, same one over here.
8
And to be honest with you, even though I know the answer, it's almost impossible for me to tell.
9
So can you figure out which one is which?
10
Well, on the right -hand side, we have the clone that I built with AI.
11
And on the left -hand side, we have the actual MongoDB Compass application.
12
Now, again, this took me 30 minutes to clone and just $13 in AI credits using a very popular package.
13
Now we're plug -in called Reverse Engineering Anything, which I want to get into.
14
So this is the GitHub repo for Reverse Engineer Anything.
15
Now it's been going viral over the past few days here.
16
It has over 344 ,000 stars, and basically it does what it says.
17
It allows you to reverse engineer anything using AI.
18
And I'm going to explain exactly how it works, but to install it is literally as easy as just copying this GitHub URL,
19
going to your agent and telling it, Hey, I want you to install reverse engineering anything, add all of the tools to cloud code,
20
and then it will add the tools and you can start using it to make clones like I just showed you.
21
So before we go into the details, let me start with how re or reverse engineer anything actually works.
22
Now when you install an app, you just get the finished product, you don't get the source code.
23
Now reverse engineering is the process of working out how that finished product works and the tools for doing that, things like decompilers and debuggers,
24
have been around for years now.
25
Now they're just really slow and they're pretty difficult to use by hand if you don't know what you're doing.
26
Now what re does is it sits in the middle.
27
So on one side, you have your coding agents like CloudCode, Codex, Cursor, whatever.
28
On the other side, you have these real reverse engineering tools like Gidara, EDA, Frida, GDB, whatever.
29
I'm probably mispronouncing them because I don't even know how to use them, but I don't have to because I now can use this tool.
30
Now, basically, you can add them into CloudCode using things like MCP servers, and then we can run all of these on your own computer,
31
do everything locally, decompile, understand the application, and give you back answers.
32
And every answer comes back with evidence.
33
So what it found, where in the app it found it, which tool found it, and what's still unknown.
34
So the agent doesn't need to guess.
35
It can actually rebuild something by looking at the exact way that it was already built.
36
Now, this is really interesting because you don't just need to do this on web apps.
37
You can do this on really any type of application, even desktop apps that typically are pretty difficult to reverse engineer.
38
So what can the agent actually do with re?
39
Well, it gets 207 different tools.
40
Now, the biggest group, which is 79 of them, is for compiled programs.
41
So things like reading decompiled code, searching for text, and finding who calls what.
42
Then there are tools for Android apps, websites, and Electron apps.
43
There's also live debugging with Frida and GDB, and a whole group for tracking evidence and checking that a rebuild actually matches the original.
44
Now, one tip if you want to try this here is
45
that those 207 tool descriptions can add up to around 270 ,000 tokens with every single message.
46
Now in Claude code, you're actually able to set an enabled tool search to true.
47
I'm going to show you how to do this in one second.
48
And that will mean the tools only load when the agent actually needs them.
49
Now for me that cut each message to about 28 ,000 tokens, which makes a massive difference when you're running this at scale.
50
Let me quickly show you.
51
So I'm just going to tell Claude code, this set enabled tool search to true for your tool calls.
52
And now this way it will start searching through the tools
53
and figuring out
54
which one it needs to use rather than looking at all of them every single time it calls an AI model.
55
So you can see it was able to update this year in our settings.
56
Now, what I want to do is show you how I ran this,
57
because again, this is the cloned application that we got here using re which is just absolutely crazy.
58
And I want to dive more into the mechanics of how this actually works.
59
So you understand where it will be useful for you.
60
Okay.
61
So to run everything that you're about to see,
62
I actually use today's sponsor open router now it's a really good fit for this because reruns can get extremely expensive.
63
Now the agent actually loops over and over again
64
and I've seen people spend you know hundreds of dollars on a single rebuilt product.
65
So what I wanted to do was compare an expensive model with a cheap one
66
which I'm going to show you the results of in a minute
67
and to do that I used open router
68
which gives me one API key and one endpoint for covering over 400 different models.
69
Now I simply just pointed cloud code at open router by changing two simple environment variables.
70
And then after that, I was able to switch to different models and see all of the pricing directly in my dashboard.
71
So you can see that every request actually shows this exact cost here in the activity page.
72
And that mattered a lot for this video because Claude Code's own estimate really overstates the cost.
73
And in this example, it overstated it by up to four
74
and a half times what it actually cost me to run this.
75
So every number that you see in this video comes directly from OpenRouter.
76
And even if a model gets rate limited halfway through a long run,
77
I can have a fallback model and move over to something else that my program doesn't completely stop.
78
If you want to try Rhea for yourself, OpenRouter is linked in the description.
79
I use it for pretty much anything where I need an API key.
80
And I have a ton of usage.
81
It's a great platform and really the best way to use AI models.
82
You also can call image, video, voice, everything from one single API key.
83
All right, so once you've got Rhea installed inside of CloudCode, you can simply just ask it to use Rhea
84
and rebuild pretty much any app that's on your computer where they can access from the web.
85
Now, if you go into your terminal -based environment to use CloudCode, you'll be able to see the MCP server.
86
So if you type
87
Cloud here, just go, yes, I trust this folder, and then type slash MCP,
88
you'll see the Rhea MCP server shows up here with 207 different tools.
89
Now, it also has some prompts and some other stuff inside of here, and basically it's ran through this kind of NPM package.
90
However, if you try to look at the MCP server from the desktop application, after you add it, you probably won't see it.
91
That's fine.
92
It's still there, but it will just appear when you start asking it to do something.
93
So if I say, Hey, rebuild the OBS application using reverse engineer, anything.
94
Then if I press enter here, it should find that connector.
95
So you see Rhea pops up right here and it will start building that out.
96
Now I won't wait for all of this to finish because I already built MongoDB Atlas,
97
but basically that's as easy as it is to start doing this.
98
So now I want to discuss what Rhea is actually doing behind the scenes, specifically when it's looking at compiled programs.
99
So things like a Windows executable file like OBS.
100
So first what the agent will do is open the binary and try to get an overview of the program.
101
So what kind of file is it?
102
What libraries it uses?
103
Where does it start?
104
Then it needs a starting point.
105
So it's going to search for text that you can actually see in the application.
106
It's like a button, a label, an error message, and it's going to jump to the code that uses that reference.
107
Then it reads that function.
108
So the decompiler is going to turn machine code back into C -like pseudocode, which the model will actually be able to read.
109
Then it's going to follow all of the calls.
110
So what calls this function?
111
What calls that function?
112
Where is the data flowing throughout the application?
113
Now, anything that it can't prove, it's going to write down as an unknown instead of just guessing.
114
And at the end of it, it's going to compare the rebuilt code against the original to check if they behave the same way.
115
Now for compiled programs, you will need a decompiler installed.
116
However, it can automatically install it for you if you just put it in bypass permissions mode.
117
Now Compass, the one that I did here, is actually a JavaScript app.
118
So it skips the decompiler because the code ships as JavaScript instead of plain machine code.
119
So for MongoDB Compass, which Claude was able to remake, I pointed Rhea at a single 49 megabyte file.
120
Now this is basically the entire app that just packaged together
121
and in under three minutes it was able to map the entire thing.
122
So it had 530 different files, over 3 ,500 code modules
123
and over 13 ,000 findings including how the app's windows actually talked to the back end
124
and how all of the communication occurred.
125
So here's what these models actually built and I say models because I ran this with two models,
126
Opus 5 .5 and Haiku 5 .5 to see what actually was the difference with an expensive, and a cheap model.
127
Now, here's exactly what happened.
128
Well, first we set everything up, right?
129
Then I gave both models the exact same prompt.
130
So I said, use RIA to figure out how
131
Compass works, how it's styled, and then rebuild it as a desktop application with these eight features.
132
This is what I included in the prompt.
133
So I wanted the ability to connect a database sidebar, browsing documents with filters and pages, inserting, editing, and deleting, schema the tab,
134
aggregations tab, and then the indexes tab.
135
And I wanted it to look exactly the same as Compass, as you guys already saw.
136
I also gave it a small test database that it could load up here that I already had built with MongoDB.
137
So here's the results that I actually got that I had Claude's screenshot.
138
So you can see Opus 5 .5 costs $13.
139
Haiku 5 .5 costs $0 .85.
140
With Opus, it took 42 minutes.
141
With Haiku, it took about 15 minutes.
142
And you can see that they look pretty similar here.
143
Now Haiku has some visual differences compared to the real compass version.
144
You can see it's a little bit simpler.
145
The icons aren't quite there, but generally it gave me pretty much the exact same stuff.
146
Just again, like a little bit of small issues with kind of the spacing and the indexes, and it wasn't quite as clean,
147
but you get the idea, right?
148
We're able to build the entire thing.
149
And when we used Opus 5 .5, it gave us a near identical clone.
150
Again, just to open this up and show you, like I can go to aggregations, I can run queries, I can view specific schemas,
151
I can look at the index.
152
I can connect to different databases.
153
Like, like how crazy is that, that this actually just works.
154
I can directly even like edit a value here and change this and save it.
155
And it works properly.
156
And this is just all done with AI with literally two or three prompts.
157
So with all of that said, what does this actually mean?
158
Well, to be honest with you, I don't really know.
159
I mean, this is super cool.
160
It's obviously very interesting that we can do this.
161
And it really shows
162
that the value of software is no longer just in writing a bunch of code like it used to be.
163
It's really more in making something that's legitimately valuable that solves a problem and then people actually want to use.
164
This leads me to believe that more and more software will just de facto become open source.
165
And the companies are probably going to be less protective of trying to guard all of their secretive code bases.
166
Because really, there's just less value in doing that now than there used to be in the past.
167
I can remember when code was sacred
168
and you wouldn't want to share certain modules or files
169
or what you're doing because you don't want anyone to get in on your secret
170
and rebuild this really technically complex app that you made.
171
Now we literally have an AI tool that can rebuild pretty much anything in a matter of few minutes and even decompile,
172
go through, run all of the compiled code.
173
It's just crazy where we're at now in 2026.
174
So I think it shapes what we use software for, what the value of software is and what we're going to look at going forward
175
but I don't believe this wipes out software engineers.
176
And to be honest, the more cool tools we get like this, the more interesting software we can build.
177
And again, in my opinion, the value of software is knowing what to build, not just building it itself,
178
having that judgment, building a nice UI, solving a legitimate problem.
179
Now, more than ever, the code is not that valuable, but being able to know what to code and having that judgment is becoming more valuable.
180
That's my opinion.
181
I don't know if you guys agree with me.
182
Let me know in the comments down below, and I will see you in another video.

הורד אפליקציה

כל מה שאתה צריך כדי לדבר בשטף

הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק

אותו ערוץ

FOR YOU

המלץ על סרטון

אוצר מילים והערות הגייה לשיעור הזה

שיעור הדיבור הזה מבוסס על הסרטון “I Tested The Viral Reverse Engineering Repo”. המילים שחוזרות הכי הרבה: code, tool, model, app, reverse. בסרטון הזה יש 182 משפטים ו-2437 מילים לתרגול Shadowing. הדיבור נמשך 11:23. הדובר מדבר מהר, כ-214 מילים בדקה, אז צפו לצלילים מחוברים ומקוצרים. 85% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית; כדאי ללמוד את השאר לפני שמתחילים.

אוצר מילים מרכזי בסרטון הזה

15 מילים מהסרטון שכדאי ללמוד, עם ההגייה והמשמעות שלהן:

מילההגייהמשמעות
compass שם עצם/ˈkʌmpəs/מַצְפֵּן
server שם עצם/ˈsɝvɚ/שָׁרָת
database שם עצם/ˈdeɪtəˌbeɪs/בְּסִיס נְתוּנִים
install פועל/ɪnˈstɔl/התקין
cloud שם עצם/ˈklaʊ̯d/עָנָן, עָב
package שם עצם/ˈpæk.ɪd͡ʒ/חֲבִילָה, אֲרִיזָה
compare פועל/kəmˈpɛɚ/השווה \ הִשְׁוָה
solve פועל/sɒlv/פָּתַר
connect פועל/kəˈnɛkt/חיבר
edit פועל/ˈɛdɪt/ערך
module שם עצם/ˈmɑd͡ʒul/מוֹדוּל
token שם עצם/ˈtoʊkən/אֲסִימוֹן, זִ׳יטוֹן
label שם עצם/ˈleɪ.bəl/תָּגִית
plain שם עצם/pleɪn/מִישׁוֹר, עֲרָבָה
terminal שם עצם/ˈtɚmɪnəl/בֵּית נְתִיבוֹת, טֶרְמִינָל

Phrasal verbs שתשמעו

מילהמשמעות
figure out פועלהֵבִין, מצא תשובה
write down פועלרָשַׁם

משפטים שכדאי לחזור עליהם

משפטים קצרים ושלמים מהסרטון שאפשר להשתמש בהם בשיחה יומיומית:

  • You can see it's a little bit simpler.
  • We're able to build the entire thing.
  • It's obviously very interesting that we can do this.
  • I don't know if you guys agree with me.

דקדוק בסרטון הזה

המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:

מבנהבסרטון
“Used to” used to + verb — הרגל או מצב שהיה נכון בעבר וכבר לא קייםused to be
סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולהis built · was already built · is linked
משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דברCompass, which is · group, which is · tokens, which makes
הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיוhave been · I've seen

הגייה ששווה לשים לב אליה

הדובר משתמש ב-38 קיצורים וצורות מקוצרות, כמו don't, I'm, you're. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.

  • הצלילים של “sh” ו-“zh”: screenshot /ˈskriːn.ʃɑt/, aggregation /æɡɹəˈɡeɪʃən/, dashboard /ˈdæʃˌboɹd/
  • מילים ארוכות — שימו לב להטעמה: legitimate /lɪˈd͡ʒɪt.ɪ.mət/, technically /ˈtɛk.nɪˌkəl.i/, decompiler /diːkəmˈpaɪlə(ɹ)/, aggregation /æɡɹəˈɡeɪʃən/, executable /ˈɛksəkjutəbl/

צלילים שדוברי עברית מתקשים בהם:

  • /w/ — שפתיים מעוגלות, לא /v/: halfway /ˌhæfˈweɪ/, wipe /waɪp/, query /ˈkwɪɹ.i/
  • /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: package /ˈpæk.ɪd͡ʒ/, variable [ˈvæɹ.i.ə.bl̩], halfway /ˌhæfˈweɪ/, mechanic /mɪˈkænɪk/, bypass /ˈbaɪpæs/
  • /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: reverse /ɹɪˈvɝs/, rebuild /ɹiːˈbɪld/, prompt /pɹɑmpt/, sacred /ˈseɪkɹɪd/, protective /pɹəˈtɛk.tɪv/

איך לתרגל עם הסרטון הזה

  1. הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
  2. התחילו במהירות 0.75×, תרגלו Shadowing משפט אחר משפט, וחזרו למהירות רגילה כשזה מרגיש קל.
  3. הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו compass, server, database.

מהי טכניקת השאדואינג?

שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.

טכניקת Shadowing: קרא את המדריך המלא שלב אחר שלב →