系統設計者的話：學英文根本不用背，你講中文，你有在背中文嗎？學英文也是一樣的道理，那是自然而然就會的東西，用背的方式最後肯定都是不行的。 更多...

最好的學習就是有英文的父母，不斷的跟你說話、耐心的教導你，時間長了，你也就慢慢就融入其中了。

但是我們沒有英文父母怎麼辦？看影片學英文就學的起來嗎？學不起來。

我們從小到大，也看過了不少英文電影，至少也看過1、200部也跑不掉，但是為什麼看了這麼多的英文電影，英文還是很爛呢？

主要的原因是我們沒有從基礎性的強化學習。舉個例子，西方的幼兒出生時，他至少聽了各種大人講英文至少聽了2年，才慢慢開始說英文、與大人互動。

而且都是一字一句慢慢的說、慢慢的教、漸進式的、慢慢的、越來越習慣、越來越聽的懂、越來越會說的過程。

那麼我們看的影片、電影過程中，都是大人成熟型的講話速度、方式、語調，我們怎麼可能跟的上？

一旦跟不上，思想中就會產生覺的好難哦、我不行種種念頭，那麼產生了這種潛在式的排斥心理作用，那麼你就更難學的會了。


所以我們必須打好基礎、深厚的基礎，萬丈高樓平地起，唯有打下深厚的基礎，後面你走的路才會越來越順。

程式界裏有句話，程式債欠的越多，最後就只能放棄。學英文也是一樣，英文單字債欠的越多，你就直接上來文法、句型、語調，最後也只能放棄。

基於上述的思維，我打造了這套系統，從最基礎的單字學習起，不斷的強化、加深你對這個單字的聽力，透過各式各樣的影片、各式各樣的人、各種不同的場景。

就只是為了訓練一個單字的聽力，無數的人跟你講同一個單字，講個20遍、50篇、100遍(且不重覆)，我就不信學不起來。


這套系統做出來後，我自己在使用的過程中，確實真的能聽出來他們講的這個單字，而且他們講的速度再快也能聽的出來。

能聽的出來，就知道他講的大概意思；能夠知道他講的大概意思，就能夠用幾個簡單的單字回應；能夠回應，也就能夠對話；當能夠對話，就能夠再修正文法、句型、語調。


我的目地就是希望自己至少能聽的懂人家在說什麼，用英文跟人家對話，大家共同努力、學習。若有其它想法或對這套系統設計的建議，也可以與我聯絡：ichich2013@gmail.com

Building Faster, More Resilient Apps with Service Worker (Chrome Dev Summit 2018)
觀看次數：492
serviceworker
tooling
and
i'm
eva
i'm
serviceworker
from
the
speed
and
our
decisions
regarding
serviceworker
positively
and
negatively
our
site's
you
said
the
serviceworker
was
serviceworker
is
now
supported
in
all
serviceworker
and
caching
we
usually
achievements
of
serviceworker
was
that
that
serviceworker
can
also
be
a
great
serviceworker
affects
the
performance
of
java
scripts
need
to
be
parsed
compiled
optimization
automatically
for
you
this
serviceworker
on
your
page
but
it's
not
overlooked
cost
of
serviceworker
is
that
it
can
take
time
for
the
serviceworker
serviceworker
just
forwards
the
request
doesn't
touch
the
cache
at
all
since
service
worker
process
isn't
currently
web
app
isn't
using
serviceworker
using
serviceworker
and
that
service
to
go
through
the
serviceworker
the
serviceworker
but
that
cost
isn't
worker
set-up
time
on
my
website
philipp
installing
the
service
worker
it's
can
be
more
like
100
to
500
milliseconds
and
at
the
95th
percentile
sometimes
instant
and
this
affects
any
caching
found
or
there's
a
timeout
or
error
like
is
very
fast
when
there's
a
cache
hit
have
a
timeout
remember
there's
also
the
timeline
and
you
can
look
at
the
entries
serviceworker
itself
you
can
use
serviceworker
over-aggressive
pre-caching
or
pre-caching
before
the
window
has
so
for
example
if
your
pre-caching
you
know
tamplin
teague
logic
when
implementations
and
given
what
we
said
with
using
serviceworker
serviceworker
so
the
first
and
arguably
site
with
serviceworker
is
an
javascript
css
and
images
that
those
serviceworker
implementations
I
found
preload
to
warm
the
http
cache
for
serviceworker
is
doing
is
pre-caching
recreating
what
the
browser
is
already
not
recommended
to
put
caching
headers
the
serviceworker
starts
up
the
optimization
that
aven
mentioned
but
not
using
a
serviceworker
and
that's
serviceworker
is
asleep
and
needs
to
navigation
sidebar
footer
and
a
lot
of
stuff
that's
change
rather
than
fetching
here's
a
visualization
of
the
streaming
response
that
combines
never
stream
and
if
the
browser
doesn't
general
streaming
cache
content
with
with
the
serviceworker
starting
up
serviceworker
boot
up
cost
that
i
the
browser
sends
the
assets
this
serviceworker
navigation
preload
header
come
directly
from
the
serviceworker
the
streaming
partials
strategy
that
I
serviceworker
to
use
navigation
preload
serviceworker
ok
of
cache
then
there
are
non-critical
strategy
for
serviceworker
is
a
great
clogging
your
users
device
so
reviewing
in
designing
and
updating
your
cache
in
assets
serviceworker
that's
usually
pre-caching
caching
is
very
similar
to
installing
a
ready-made
package
with
your
app
it's
runtime
caching
on
the
other
hand
is
really
great
for
non-critical
assets
user
has
user
interacts
with
the
app
the
when
the
user
navigates
to
a
new
grows
to
300
kilobytes
and
so
on
and
so
on
as
the
user
interacts
with
my
app
the
app
throughout
the
runtime
phil
can
we
do
it
programmatically
somehow
you
can
allows
us
to
proactively
control
the
app
can't
just
throw
assets
into
the
cache
non-critical
assets
into
different
can
evict
the
non-critical
ones
when
conditionally
or
you
can
put
size
or
can
also
configure
the
plugin
to
automatically
purge
all
event
all
entries
if
there's
any
kind
of
quota
you
have
a
non-critical
asset
cache
ok
your
serviceworker
updates
it's
very
other
you
can
use
the
content-based
pre-caching
package
you
don't
have
to
backgrounds
they
can
use
our
app
at
home
or
on-the-go
keep
in
mind
those
underpowered
devices
time
if
used
runtime
caching
and
plan
can
use
in
your
decision-making
for
speculatively
pre-caching
future
turned
on
when
user
enables
this
feature
assets
similarly
you
can
use
the
network
scenarios
where
you
give
the
user
the
button
where
user
can
explicitly
opt
in
I
know
we've
presented
a
lot
of
content
andras
serviceworker
to
a
site
will
magically
optimization
plan
reinvent
the
http
cache
inside
of
your
serviceworker
and
don't
just
cache
doing
you're
not
actually
optimizing
your
site
for
serviceworker
and
you
implementations
and
make
future

相關影片

加Line好友 每日8AM 推播1單字

加入好友

其他人正在學習的單字

1. stars
2024-05-04 21:26
2. play
2024-05-04 21:26
3. received
2024-05-04 21:26
4. businessyour
2024-05-04 21:26
5. powerand
2024-05-04 21:26
6. annulled
2024-05-04 21:26
7. registered
2024-05-04 21:26
8. runner-up
2024-05-04 21:26
9. were
2024-05-04 21:26
10. behalf
2024-05-04 21:26
11. hug
2024-05-04 21:26
12. you
2024-05-04 21:26
13. gathered
2024-05-04 21:26
14. temporal
2024-05-04 21:26
15. flurry
2024-05-04 21:26

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜