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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

Instant Loading with Service Workers (Chrome Dev Summit 2015)
觀看次數：337
so
hi
i'm
jeff
posnick
from
the
chrome
developer
relations
team
we've
heard
a
serviceworker
caching
as
progressive
enhancement
so
during
the
session
we'll
shell
pass
serviceworker
model
real-world
example
so
I
build
a
web
app
applications
and
in
the
screencast
we're
user
discovers
on
the
web
as
a
search
app
Engine
instance
we've
deployed
on
and
we're
showing
off
top-level
cache
and
no
serviceworker
in
place
yet
respectable
of
650
milliseconds
so
let's
we're
able
to
get
the
above-the-fold
cache
but
without
a
serviceworker
maybe
because
your
browser
doesn't
support
it
takes
around
560
milliseconds
milliseconds
with
the
same
cache
content
but
without
a
serviceworker
we're
looking
about
650
milliseconds
to
get
requesting
or
I
fix
the
demo
app
for
the
first
time
with
no
serviceworker
and
milliseconds
before
we
get
our
full
cache
it
only
takes
five
milliseconds
with
the
serviceworker
and
with
the
build
web
apps
that
consistently
load
in
tomorrow's
sessions
but
keep
that
in
one-second
delay
in
page
load
times
can
concepts
you'll
need
to
understand
so
is
the
html
javascript
css
and
any
other
discoverability
of
the
web
and
unlike
what's
the
serviceworker
technically
speaking
a
serviceworker
you
know
it's
a
network
proxy
written
in
javascript
and
intercepts
rach
http
requests
made
from
network
runway
and
let's
walk
through
the
contents
of
site-wide
inline
styles
they'll
be
have
a
template
insertion
point
and
kind
of
as
a
placeholder
for
the
client-side
templating
that
will
take
contains
all
the
site-wide
javascript
cache
cleanup
of
any
out-of-date
your
serviceworker
enters
into
an
idle
andras
server-side
rendering
when
there's
a
url
pattern
that's
routed
to
a
matching
client-side
in
the
app
show
that
ends
up
the
advantages
of
structuring
your
web
library
we'll
talk
about
is
sw-toolbox
of
all
the
runtime
caching
strategies
they've
powered
the
serviceworker
for
this
year's
Google
i/o
web
app
so
sw-precache
so
most
web
apps
already
sw-precache
works
equally
well
with
step
that
runs
sw-precache
for
us
sw-precache
is
configured
with
some
wild
serviceworker
triggers
a
pre
caching
of
deployment
it'll
regenerate
in
the
serviceworker
j/s
file
since
-
the
files
logic
in
the
generated
serviceworker
you
and
automatically
update
the
cache
as
a
native
app
stores
incremental
grunt
can
install
the
sw-precache
module
globally
from
npm
and
then
run
it
using
sw-precache
and
the
ifixit
web
app
babel
saiki
use
all
sorts
of
es2015
good
the
dynamic
url
to
dependencies
option
inline
contents
of
slash
shell
next
we
file
will
automatically
serve
the
contents
of
slash
show
whenever
there's
client-side
url
routing
will
handle
finally
we
have
the
import
scripts
alright
so
sw-toolbox
basically
and
well
sw-precache
sw-toolbox
is
loaded
by
your
serviceworker
at
one
time
and
there
a
sw-toolbox
provides
a
canonical
serviceworker
check
the
cache
for
a
to
sw
toolboxes
cache
first
handler
corresponds
to
sw
toolboxes
Network
first
to
handler
so
finally
here's
an
if
it's
strategically
here
you
need
to
just
one
sw-toolbox
is
routing
syntax
yourself
so
why
use
sw-toolbox
options
make
serviceworker
caching
much
more
useful
in
real-world
scenarios
so
everyone
hears
encounted
countered
wi-fi
cache
first
we
don't
have
responsive
Network
they'll
automatically
fall
back
to
the
cache
you're
probably
cashing
those
page
ever-increasing
amount
of
storage
so
here
we
have
sw-toolbox
could
say
automatically
expire
in
sw-precache
alright
so
first
we
automatically
returning
like
stale
keeping
our
caches
up-to-date
in
the
automatically
be
expired
all
right
so
progressive
enhancement
and
that
applies
deliberately
and
I
wouldn't
really
want
browsers
that
don't
support
service
there's
a
service
worker
in
your
browser
using
far-future
http
cache
expiration
headers
this
that
setup
but
if
you
are
in
a
browser
safely
with
just
http
cache
headers
if
23
milliseconds
to
retrieve
your
landing
page
and
5
milliseconds
hen
if
you
use
the
underlying
partials
or
inline
frameworks
you're
using
but
the
concept
serviceworker
to
your
existing
web
app
using
sw-precache
and
sw-toolbox
finished
real-world
example
here's
the
javascript
both
server
and
client-side
rendering
and
can
be
adapted
to
go
those
who
prefer
a
step-by-step
hands-on
sw-precache
to
an
existing
web
apps
want
to
mention
a
polymer-based
demo
a
serviceworker
model
in
a
blog
web
app
addy
osmani
and
matt
gaunt
spent
a
great
serviceworker
set
up
with
minimal
opinions
about
frameworks
or
libraries
I
serviceworker
model
is
the
best
way
to

相關影片

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

加入好友

其他人正在學習的單字

1. something
2024-05-02 11:16
2. analyst
2024-05-02 11:16
3. revenge
2024-05-02 11:16
4. competitor
2024-05-02 11:16
5. reveal
2024-05-02 11:16
6. enjoy
2024-05-02 11:16
7. finds
2024-05-02 11:16
8. discussed
2024-05-02 11:15
9. illustrate
2024-05-02 11:15
10. brawl
2024-05-02 11:15
11. ads
2024-05-02 11:15
12. also
2024-05-02 11:15
13. banking
2024-05-02 11:15
14. drawn
2024-05-02 11:15
15. deborah
2024-05-02 11:15

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜