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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

[JSConfEU 2010] Douglas Crockford: Loopage
觀看次數：472
was
explicitly
disposing
of
memory
and
collection
is
it's
not
a
programmer
it's
a
way
of
guaranteeing
that
a
large
important
class
of
dangling
pointer
errors
cannot
occur
and
it's
only
when
okay
for
c++
programmers
to
be
conveniences
for
that
but
I
tend
to
true
or
for
semicolon
semicolon
but
they
higher-level
things
in
terms
of
that
having
it
similarly
we've
got
do
while
into
recursive
functions
so
here
i'm
doesn't
quite
work
in
javascript
right
javascript
does
not
currently
implement
tail
recursion
optimization
so
you'll
callback
functions
and
those
functions
clicking
and
mousing
and
keyboarding
and
browser
got
brilliantly
right
with
a
they
stop
the
main
browser
threads
and
those
restrictions
the
browser
got
all
mathematician
she
thought
should
be
wasn't
going
to
work
that
programming
compiler
we
call
things
compilers
today
more
like
a
linker
or
a
loader
than
it
compiler
and
it
went
through
iterations
renamed
as
mathematic
it
was
one
of
the
turns
out
fortran
made
programmers
much
be
a
recurring
theme
that
very
often
characteristics
in
both
math
magic
or
mathematic
and
fortran
was
blocking
read
was
completed
the
model
for
i/o
and
in
teletypes
and
interactive
devices
so
flow
of
the
dialogue
was
dictated
by
the
use
than
today's
programs
time-sharing
environments
including
embedded
systems
people
use
so
effectively
it
has
didn't
reach
that
idea
didn't
reach
eighty-four
in
1984
macintosh
which
was
the
first
reasonably
priced
computer
and
affordances
for
creating
menu
bars
point
except
for
hypercard
Bill
atkinson
multi-level
macpaint
in
which
he
could
non-programmers
found
that
they
could
be
netscape
navigator
to
was
combining
is
with
javascript
the
dom
is
really
javascript
does
not
have
read
it's
one
loops
so
javascript
programmers
are
threading
and
threading
is
the
most
of
most
programmers
today
so
everything's
a
trade-off
there
nothing
at
the
trade-offs
with
threading
on
the
threads
isn't
so
we
can
do
multiple
we've
got
to
javascript
programs
each
is
any
time
you
have
a
read-modify-write
threads
as
being
cars
or
but
they're
there's
no
way
to
predict
how
they're
unreliable
it's
about
all
you
can
do
is
say
oh
you're
using
threads
there's
your
sometimes
called
semaphores
or
monitors
section
are
blocked
if
the
threads
don't
problem
there's
the
deadlock
problem
where
you've
got
two
or
more
threads
be
gridlock
we've
got
a
bunch
of
cars
the
same
time
this
is
sal
paulo
brazil
they're
all
stuck
everybody's
waiting
threads
and
synchronization
deadlock
is
they're
going
to
occur
and
once
they've
occur
predictably
then
you
can
doesn't
come
for
free
there's
the
threat
of
deadlock
which
will
just
kill
threads
threads
eventually
strangling
the
whole
java
was
that
it
couldn't
make
up
its
reliability
hazards
of
threads
and
that
advantages
of
workers
is
there's
no
which
combines
two
great
ideas
functions
and
networking
produces
a
really
bad
browser
of
the
client
while
we're
subject
to
cross-site
scripting
attacks
cross-site
scripting
has
two
causes
the
terrible
there's
also
misinterpret
misinterpretation
of
html
html
is
such
a
html5
ignores
and
worsens
the
xss
said
that
html5
doesn't
ever
have
markup
injection
vulnerabilities
which
is
wrong
the
browser
is
a
loaded
gun
aimed
at
trigger
so
page
templates
the
a
template
is
to
richard
a
framework
to
server-side
programming
as
well
it
netscape
offered
a
server-side
javascript
product
in
1996
and
it
was
so
it
had
all
the
disadvantages
of
the
other
page
template
assist
amande
at
the
the
front-runner
right
now
a
high-performance
event
pump
it
it
synchronous
functions
which
do
block
though
j/s
with
a
pseudo
dom
so
we
can
the
callbacks
to
fire
and
once
they've
we've
got
a
really
nice
fallback
story
sessions
reliability
packet
reordering
of
that
we're
trying
to
do
messaging
in
http
which
has
a
lot
of
beneficence
e
in
of
http
and
runny
jack's
on
top
of
tcp
I
various
implementations
of
having
some
relational
model
but
you
don't
have
to
database
in
productions
of
1996
so
these
javascript
variables
which
are
enclosures
bound
to
the
event
handlers
because
it's
just
in
variables
so
it's
recursion
for
looping
which
would
have
he'd
never
used
continuation
passing
stuff
as
long
as
i've
been
a
programmer
why
we
shouldn't
do
event
programming
languages
why
we
don't
need
recursion
why
we
don't
need
closure
and
functions
javascript
which
is
amazing
javascript
tolerate
to
language
which
we're
ie9
than
any
other
browser
so
kudos
to
microsoft
told
us
that
they
don't
intend
terrible
portability
terrible
but
with
javascript
somehow
we've
made
that's
why
it's
so
distressing
that
compliant
demonstrating
or
time
are
you
here
i'm
the
ability
using
yui
3
on
nodejs
you're
of
the
computation
so
far
and
so
it's
optimization
or
proper
tail
calls
backwards
debugging
becomes
more
that's
a
trade-off
some
people
have
you're
debugging
but
that
means
any
recursion
would
fail
when
you're
debugging
and
so
that
doesn't
actually
solve
anything
so
it's
a
hard
trade-off
debugger
could
instead
of
relying
on
the
corrected
the
cross-site
scripting
capabilities
so
in
my
view
html5
makes
they're
more
places
that
the
attackers
firewall
or
wherever
else
and
that's
html5
and
it's
nice
that
we're
moving
their
priorities
wrong
and
they're
doing
much
all
of
html5
ones
that
microsoft
actually
participated
in
tc39
right
was

相關影片

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

加入好友

其他人正在學習的單字

1. kind
2024-05-01 19:49
2. nearby
2024-05-01 19:49
3. sit
2024-05-01 19:49
4. support
2024-05-01 19:49
5. Christmas
2024-05-01 19:49
6. share
2024-05-01 19:49
7. key
2024-05-01 19:48
8. then
2024-05-01 19:48
9. room
2024-05-01 19:48
10. assume
2024-05-01 19:48
11. boring
2024-05-01 19:48
12. deeply
2024-05-01 19:48
13. chord
2024-05-01 19:48
14. business
2024-05-01 19:48
15. anymore
2024-05-01 19:48

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜