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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

May We Help You? Tools and Libraries for Progressive Web Apps (Chrome Dev Summit 2016)
觀看次數：431
i'm
jeff
posnick
from
google's
developer
you'd
be
tempting
to
just
you
know
copy
to
be
precast
here
are
stored
in
an
previously
pre
cached
instead
of
reusing
the
entries
that
haven't
changed
and
this
of
a
fetch
handler
that
performs
runtime
catching
and
in
this
case
it's
never
cleans
up
entries
so
you
may
not
just
ignores
the
kesha
expiration
h2b
response
headers
you
know
when
you're
things
like
that
and
automatically
clog
up
every
user's
device
with
larger
building
a
production-ready
service
changed
are
invalidated
and
downloaded
runtime
caches
you
might
use
maximum
both
and
this
prevents
your
caches
from
production-ready
a
checklist
items
are
not
surprisingly
the
answer
is
tooling
tongue-in-cheek
text
on
the
slide
i'm
production-ready
service
worker
okay
so
first
is
sw
prakash
it's
a
build
time
serviceworker
file
for
you
so
the
there's
also
a
scoby
toolbox
and
this
is
a
runtime
library
that
extends
the
caching
strategies
jakes
offline
cookbook
and
copy
and
stillwell
revalidate
strategy
you
can
caches
so
sob
precache
and
sob
toolbox
caching
and
the
runtime
caching
for
your
a
few
projects
that
are
pre-configured
Toby
precash
now
some
of
your
toolbox
offline
first
by
default
I
said
polymer
components
and
the
serviceworker
to
maintain
the
sw
precash
webpack
command-line
interface
that
can
be
used
they're
using
sw
precash
in
sw
toolbox
specific
settings
to
see
how
they're
has
automatically
pre
cached
and
cache
entries
are
automatically
versioned
and
kept
up
to
date
by
the
serviceworker
runtime
caching
configuration
this
is
tells
sw
precash
to
automatically
surfer
serviceworker
file
and
to
a
library
that
automatically
queues
and
retries
Google
analytics
hits
that
take
offline
so
they're
using
sw
off
on
handlers
that
automatically
Q
any
filled
was
offline
all
right
so
you've
seen
a
library's
to
generate
a
serviceworker
serviceworker
effectively
so
if
you've
serviceworker
is
behaving
as
expected
so
chrome
extension
interface
run
against
highlighted
section
that
they're
pwa
has
app
world
of
devices
on
real
world
networks
production
s
to
be
pre
cashin
smu
toolbox
deployments
so
here's
just
a
to
use
and
battle-tested
but
the
flip
deprecated
we're
not
duplicating
a
few
of
our
high-level
goals
for
this
small
bit
of
functionality
like
cash
to
using
all
the
functionality
should
we're
thinking
conceptually
we
split
the
runtime
handlers
and
request
behaviors
so
here's
an
overview
of
each
of
those
of
requests
so
we're
envisioning
built-in
classes
to
handle
like
regular
similar
to
how
sw
toolbox
is
currently
configured
for
runtime
caching
the
router
class
also
lays
the
groundwork
layer
from
routing
is
our
runtime
handler
layer
and
this
is
sub
classes
that
implement
common
runtime
caching
won't
modify
the
out-going
request
and
different
behaviors
to
customize
those
configure
the
runtime
handlers
and
take
more
custom
callbacks
that
the
runtime
fetch
fetched
it
fail
and
cashed
it
lifecycle
prior
to
contacting
the
network
a
runtime
handler
will
trigger
to
fail
any
fetch
did
callback
handler
the
behaviors
we're
planning
to
callbacks
and
triggers
so
first
we're
exploring
responsive
image
behavior
that
current
devices
capabilities
into
rhythms
of
the
cash
you'd
be
able
to
configure
our
caching
and
also
to
configure
the
type
of
callbacks
that
are
update
behavior
next
we're
configuring
a
route
to
automatically
apply
a
handler
ends
in
jason
and
if
there's
a
match
handler
using
the
wrapper
that
we
just
configured
for
that
cache
behavior
so
to
configure
a
new
router
and
this
also
for
other
requests
and
aren't
explicitly
currently
use
sw
precache
for
and
it
ways
of
automatically
integrating
into
production-ready
approach
to
using
firebase
Cloud
messaging
push
love
and
he'll
be
demonstrating
a
bit
these
tools
and
build
a
production-ready

相關影片

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

加入好友

其他人正在學習的單字

1. next
2024-04-27 18:49
2. crisis
2024-04-27 18:49
3. search
2024-04-27 18:49
4. pieces
2024-04-27 18:49
5. available
2024-04-27 18:48
6. paste
2024-04-27 18:48
7. quicklywith
2024-04-27 18:48
8. duplicate
2024-04-27 18:48
9. ability
2024-04-27 18:48
10. battery
2024-04-27 18:48
11. apocalypse
2024-04-27 18:48
12. special
2024-04-27 18:48
13. me
2024-04-27 18:48
14. song
2024-04-27 18:47
15. doctoryeah
2024-04-27 18:47

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜