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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

Pete Hunt: React: Rethinking best practices -- JSConf EU 2013
觀看次數：528
sarcastic
responses
on
twitter
a
little
we
weren't
really
communicating
what
we
client-side
so
i'm
going
to
talk
to
you
components
not
templates
if
you
want
to
think
about
this
cynically
we're
talking
reusable
components
that
know
how
to
pocalypse
of
1999
where
we
were
putting
table
rendering
code
but
let's
talk
reducing
coupling
and
increasing
cohesion
coupling
and
cohesion
they're
functionality
how
often
do
you
have
to
symptoms
of
coupling
and
that's
what
basically
grouping
related
functionality
that
tries
to
augment
the
dom
or
html
angular
directives
also
fall
into
this
and
it's
not
just
client-side
either
it's
some
server-side
systems
as
well
templating
systems
you
have
to
add
a
underpowered
so
i'm
going
to
show
you
a
being
underpowered
and
the
first
handlebars
sorry
tom
so
first
of
all
handlebars
is
an
excellent
frameworks
but
it's
an
implementation
of
templates
so
they
reuse
a
template
you
tend
to
use
one
template
and
embeds
it
in
another
template
now
that
embedding
puts
all
of
recurring
theme
of
my
talk
another
don't
have
reduce
it's
it's
hard
to
do
branching
and
frameworks
have
solved
another
symptom
is
if
you're
continually
inventing
new
concepts
so
javascript
is
based
programming
model
language
aming
languages
and
has
kind
of
battle-tested
how
functions
work
it's
very
clear
prototypical
inheritance
most
people
abstractions
on
top
of
you
know
html
you
expressiveness
you
need
to
build
real
quote
out
from
the
angular
docs
and
i've
highlighted
every
concept
that
they've
javascript
and
it's
based
on
the
idea
that
they
want
to
augment
html
to
support
two-way
data-binding
and
in
of
scopes
you
have
to
rethink
the
idea
of
composability
directives
and
train
that's
loosely
coupled
with
other
components
coupling
and
cohesion
functionality
so
in
react
we
created
a
functionality
in
javascript
we
wanted
to
there
reusable
components
are
great
code
how
awesome
could
reuse
is
composability
expressions
in
the
dom
i've
talked
about
logic
that
generates
the
mark-up
that
components
small
because
we're
trained
other
javascript
code
why
can't
we
do
it
logic
in
your
components
i'm
not
and
javascript
is
cross-site
scripting
vulnerabilities
so
a
lot
of
times
people
do
string
concatenation
to
generate
strings
collections
that
kind
of
thing
generate
descriptions
of
the
dom
the
designers
which
is
an
optional
preprocessor
it's
a
that's
all
it
does
we're
not
reinventing
a
4x
there's
no
runtime
that
supports
this
we're
simply
taking
expressions
your
linting
tools
on
your
markup
and
tweaking
the
box-shadow
of
all
of
my
it's
the
accessibility
of
templates
and
the
power
of
javascript
the
accessibility
of
templates
in
the
power
components
and
it's
not
about
templates
ui
elements
designers
can't
make
up
another
one
crazy
environments
if
a
dom
geared
to
master
static
relations
and
evolving
in
time
are
relatively
poorly
let's
say
it's
a
you
know
a
to-do
list
react
components
are
just
item
potent
simple
because
it's
so
declarative
every
declarative
work
but
re-rendering
all
of
virtual
dom
to
make
rear-ending
on
every
and
reflow
of
my
ui
I
don't
want
to
use
minimal
set
of
dom
mutations
and
we'd
the
dhoom
3
engine
which
executes
the
which
generates
the
opengl
operations
that
then
get
flushed
to
the
graphics
a
incremental
level
you
can't
and
because
you're
building
components
and
components
we
batch
reads
and
writes
for
java
or
javascript
managing
memory
and
it's
it's
a
pluggable
part
of
our
core
events
are
compliant
to
the
w3c
consistently
across
all
browsers
now
we
yesterday
about
two-way
data-binding
we
provide
optimisation
hooks
that
don't
coupling
between
components
rethink
how
you
fundamentally
architected
your
app
phonegap
users
would
use
the
bottleneck
phantom
j/s
they're
running
their
javascript
and
then
they're
dumping
a
the
javascript
is
downloaded
the
because
you're
building
components
that
different
method
of
emptying
dom
nodes
j/s
to
test
your
components
you
can
if
interactive
charts
in
the
same
interactive
ui
on
the
same
you
just
renders
your
whole
app
in
a
webworker
implications
so
let's
talk
about
the
key
you
to
build
components
not
templates
khan
for
having
me
that's
it

相關影片

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

加入好友

其他人正在學習的單字

1. company
2025-05-06 03:14
2. scrape
2025-05-06 03:14
3. wonderful
2025-05-06 03:14
4. waits
2025-05-06 03:14
5. mathematicians
2025-05-06 03:14
6. matches
2025-05-06 03:14
7. supply
2025-05-06 03:14
8. women
2025-05-06 03:14
9. award
2025-05-06 03:14
10. economy
2025-05-06 03:14
11. unloading
2025-05-06 03:14
12. regard
2025-05-06 03:14
13. agenda
2025-05-06 03:14
14. disease
2025-05-06 03:13
15. nurse
2025-05-06 03:13

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜