シャドーイング練習: Day 26 of English Speaking Practice - 動画で英語スピーキングを学ぶ

Hello everyone so this is another day of my daily practice and today I want to talk about middleware

which is express framework topic and it is related with our last springboard topic also right

so let's start so what is a middleware what is the need of middleware right

so it is a very important topic of express and almost every real world application use this concept of middleware

so what is this a middle there right

so it is a one type of function one type of method

which will which will trigger which will coming to work between the browser

and between the user and express us so a server right

so when you give a new API

and hit enter then respected response you will see on the browser right

and you think that

when you hit API then it will go to the particular API function it will go

and call this particular API

and give you the response direct directly from the user to a browser

or from browser to a server but in real world this is not happen right

because of all the some type of validation and this thing

so for in real world once you write api

and hit enter then first your browser call a middleware

if the middle you have defined a middleware for this particular api then your browser then

call this middleware after the after the middleware it calls the next middleware

and after all the middleware has called then after

that it will go to the correct API function

and give your response so this is a one type of function one type of code

where trigger between your response and between your request and response right to pass middleware to

Between a function we use on the function like app dot use

right and To One middleware to another middleware we use a next function

So between a client request and final response all the middleware will be triggered

And now you think that what is the need of this middleware, right?

so I give you the example that you have a big application

or a website and it's a very more

and more API endpoint like assume that 100 API endpoint

so you think

that I want to maintain all the history of API code I want to maintain all the API response and requests

so you want to log all the requests like whatever api

is called by a client then you see in your console

that which is a trigger so there is a one the

so you write a console.log an api name

and this thing this particular line you have to write all the api for right

so you have to write 100 time for all api

so it is just uh you think it is just a line right we are copy paste copy paste

but in a real word it is uh not for a

particular line it can be for a validation function request validation whether the request is valid

or not whether the user is authenticated or not right

so i'll give you another example from my hospital project

that you trigger a apis for a admin right

and you have login with the person then first

when a epi function is a call the all the middleware will check whether you user is valid

or not the user is valid

and api is for admin a user is uh i mean user is patient

and api is for admin right so it is error then middleware should throw to not

access denied error

so you have to define all these validation functions all the request parameter whether it is valid

or not and this big stuff for all your 100 api calls right

so it it becomes very busy it becomes very messy

and very big code very lengthy code right

so that's why all the scenario with this middleware will work right

if you have put the middleware between particular these api then you need to write the whole code

and only for once time right and for After all the API, your middleware first trigger and then after your function call that happen.

So this is the main use of the middleware function to validate user authenticate

or not all the request parameter request body and this thing.

So there is one function next.

So it is a very important function without this function you cannot move to your next middleware

or your next response API function function so

if you are not use next function then your browser keep loading

and you stuck at a particular middleware you cannot go forward

so that's why it is use of mandatory for all the middleware right

so this is about middleware

and yes it is as similar as java of solid filter

chain in concept right in java we have learned what is the filter what is the filter chain

and this middleware and this filter then as similar as that right

so in java there is a multiple of filter a filter

one filter two filters there is a chain of filter

and at the end we got our response

and here there is a chain of a middleware one middleware two middleware

and at the end we got our response so both are similar so i have first studied about java filter

and now i'm studying about middleware

so for me it is a very uh easy topic right

if you are new then you think

that is some type of uh you can say some type of difficulties

but it is not difficult once you master it

and you also think it is very topic is it okay

so this is about a middle right so thank you for today

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

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

シャドーイング練習: Day 26 of English Speaking Practice - 動画で英語スピーキングを学ぶ

このビデオで話す練習をする理由

文法と表現のコンテキスト

一般的な発音の罠

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