シャドーイング練習: Design Patterns in Java Theory - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

各モードは全画面の練習ルームで開きます。

96 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
1
Welcome back aliens this is Navin Reddy from Telescoot Learnings and today we'll discuss something about design patterns.
2
Now you know
3
when you you can build your own software right of course anyone can build a software
4
and to develop a software what we should know is programming language right
5
and one of the best language to learn so that you can build a software is Java of course right.
6
Now let's say you want to be a software developer
7
so what you will do you will spend one week
8
and then you will learn Java
9
and the next week you start making softwares awesome right but
10
when you build a software you have to face lots of
11
problems now this problems there are some problems out of this
12
which are very common problem which has which
13
which are faced by lots of software developers so what if
14
if you have a common problem can we just solve it
15
and then anyone having the same problem can use that can use
16
that solution of course right we can do
17
that provided that's not a domain problem example
18
when you're working on a banking application so that's a different domain
19
when you're working with maybe a social networking app that's a different domain
20
but if you talk about the conceptual
21
which is object oriented conceptual problems we can solve
22
that with the help of some common solution and now
23
so throughout the industry we have some professionals they provided something called as best practices
24
and we call those best practices as design pattern.
25
So it all started in 1994.
26
So there was a book by four people and in
27
which they have mentioned the principles of design pattern or principles of object-oriented design patterns.
28
So the main motto was just to
29
so whenever you have object-oriented software the first principle was you should always prefer composition over inheritance
30
and the second principle was whenever you code, code for interface not for the implementation
31
and depend about these two lines they created the whole set of design patterns
32
and these four people were commonly known as gang of four goons right
33
so we have gang of four people so we have this four people
34
and now so they have defined some design patterns so
35
and we have just classified those design patterns of three sections
36
so we have this truck the creational design pattern we have structure
37
and then we have behavioral so we have lots of design pattern right
38
so now if you want to build software using best practices follow this design pattern
39
but there are two questions now the first question is should we know all design patterns
40
and the answer is yes you should know all the design
41
patterns the second question should we implement all these design pattern of course right
42
so let's say
43
when you are building a next software now you will be
44
using all design pattern right hold on that's not the case you should not use all design pattern in one on software, it should depend upon your requirement.
45
Look at your requirement.
46
If your requirement says, we want to create an object, how to get an object, then we have to follow creation design pattern.
47
Right?
48
Let's say I want to write a software in which you want to compose objects.
49
So let's say you have an object inside
50
that you want to include one more object or if you have an object here which provides some features, you have object here which provides some features and this object wants to use this object,
51
then we have to work with structural design patterns.
52
The third one is let's say you have two objects we don't want to compose them
53
but we want to make some communication between those two objects.
54
At this point you have to use behavioral design pattern right
55
so it all depends upon your requirement don't rush of don't rush to use design patterns.
56
Think about your logic
57
or think about your problem think about your software problem try
58
to solve those problem with the help of best practices
59
which is design pattern here and you can use any of this
60
so approximately we have 13 23 design patterns we have some more
61
but this is basic design patterns you have here okay
62
so let's start the first one we have creation design pattern
63
so in which you have six
64
or five design patterns one of the my favorite is factory pattern
65
so when you if you're working with spring framework
66
if you're working with hibernate you know about what is factory
67
right uh then we have singleton you can create only one instance of a class amazing right?
68
No one use it now.
69
So we have all the design pattern here for the creational.
70
Because here your concern is about creating the object.
71
How to create an object?
72
Maybe using factory, maybe using singleton.
73
So it's all about creation of the object the next one is structural now what it means
74
so if you have again two objects
75
and you want to compose this object inside your object then you can use structural
76
so if you are a Android developer
77
if you have worked on swing you might be knowing about
78
adapter design pattern right we after with this we have lots of design patterns one of my favorite is Fasar
79
In Hindi we have this kahawat, Sare Fasad Ki Jari Yei Hai That's Fasad Design Pattern here.
80
If you don't know Hindi that's okay.
81
That's what a weird, pakav joke.
82
So we have Structural Design Pattern which we have 6.
83
We have 7 design patterns here.
84
The next one is Behavioral.
85
In which we have, I don't know how to call this.
86
I guess this is 11 design patterns.
87
So in which we'll talk about Observer Design Pattern design pattern we'll talk about visual design patterns
88
so we will try to cover all design patterns i will try to cover everything
89
but basic ones will be there okay just just to make you understand how to use design patterns
90
so this is design patterns and
91
if you want to know the actual implementation of it
92
that we'll see in the whole series we'll talk about one by one design patterns okay
93
so make sure you subscribe the channel so
94
that you will watch all the design pattern and thank you
95
so much for watching and if you have any doubts any concern about
96
design patterns make sure you comment so that I will try to answer that questions

アプリをダウンロード

流暢に話すために必要なすべて

AI発音採点文ごとに採点
IPA練習すべての音をマスター
単語学習自分の単語帳を作る
単語ゲーム遊びながら覚える

同じチャンネル

FOR YOU

おすすめ動画

このレッスンの語彙とスピーキングのポイント

このB2レベルのスピーキングレッスンは、動画「Design Patterns in Java Theory」を教材にしています。 繰り返し出てくる語は次のとおりです:pattern, design, object, software, build。 この動画には、シャドーイング用の文が96文、単語が1097語あります。 音声の長さは5:37です。 話す速さは速く、1分あたり約196語です。音のつながりや弱く発音される音が多くなります。 単語の88%は英語の頻出3,000語に含まれるため、語彙は分かりやすいです。

この動画の重要語彙

動画の中で特に難しい単語10語を、発音と意味つきで紹介します。

単語発音意味
depend 動詞/dɪˈpɛnd/依存する
conceptual 形容詞/kənˈsɛp.tjʊəl/概念的
classify 動詞/ˈklæs.əˌfaɪ/分類する
hibernate 動詞/ˈhaɪbəɹˌneɪt/冬眠する
adapter 名詞/əˈdæptəɹ/アダプター
motto 名詞/ˈmɑ.toʊ/モットー, 座右の銘
inheritance 名詞/ɪnˈhɛɹɪtəns/遺産
subscribe 動詞/səbˈskɹaɪb/購読する
interface 名詞/ˈɪn(t)ɚˌfeɪs/インターフェース
implement 動詞/ˈɪmpləmənt/実行する, 実現する

この動画の文法

話し手がよく使っている文型を、動画の実際の表現とともに紹介します。

文型動画での表現
現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係しているhave mentioned · have defined · have just classified
受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てるare faced · were commonly known · is let

注意したい発音

話し手はdon't, we'll, you'reなど、短縮形や弱形を14回使っています。聞こえたとおりの短い形で発音しましょう。

  • 「sh」と「zh」の音: structural /ˈstɹʌk(t͡)ʃəɹəl/, creational /kɹiˈeɪʃ(ə)n(ə)l/
  • 長い単語(アクセントの位置に注意): behavioral /bɪˈheɪvjəɹəl/, developer /dɪˈvɛləpɚ/, creational /kɹiˈeɪʃ(ə)n(ə)l/, inheritance /ɪnˈhɛɹɪtəns/

日本語話者が苦手な音:

  • /r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: structural /ˈstɹʌk(t͡)ʃəɹəl/, behavioral /bɪˈheɪvjəɹəl/, creational /kɹiˈeɪʃ(ə)n(ə)l/
  • /v/ — /b/ にならないように、上の歯を下唇に当てる: behavioral /bɪˈheɪvjəɹəl/, developer /dɪˈvɛləpɚ/
  • /f/ — 「フ」ではなく、上の歯と下唇で出す: classify /ˈklæs.əˌfaɪ/, interface /ˈɪn(t)ɚˌfeɪs/

この動画での練習方法

  1. まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
  2. まず0.75倍速で一文ずつシャドーイングし、慣れてきたら通常の速度に戻します。
  3. 自分の声を録音して元の音声と比べます。depend, conceptual, classifyなどの単語に特に注意しましょう。

シャドーイングとは?英語上達に効果的な理由

シャドーイング(Shadowing)は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的:ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影(shadow)」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →