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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

Pete Hunt: React - Rethinking Best Practices (updated) - JSConf.Asia 2013
觀看次數：523
sourcing
at
jas
conf
us
in
May
and
we
got
some
sarcastic
reactions
to
it
that
library
for
creating
user
interfaces
to
depending
on
your
definition
of
mvc
to
focus
on
some
prerequisites
so
we
is
building
components
and
not
templates
has
anybody
used
a
client-side
templating
library
like
handlebars
is
a
cynically
we
like
to
think
of
components
using
a
template
so
a
templating
directives
and
spits
out
some
static
are
concerns
there
it's
very
ill-defined
about
reducing
coupling
and
increasing
cohesion
so
coupling
is
the
degree
to
that
are
constrained
to
a
single
these
cascading
changes
and
they're
a
is
cohesion
so
cohesion
is
the
degree
to
it's
also
not
going
to
be
maintainable
it's
not
just
templates
it's
anything
really
make
it
interactive
so
angularjs
style
directives
also
fall
behaves
I
go
to
the
javascript
file
with
the
template
and
change
the
template
logic
in
the
template
so
the
template
is
from
javascript
write
javascript
fetches
to
do
and
then
the
template
renders
it
implement
a
zebra-striped
alternating
row
colors
with
a
template
a
model
is
synced
between
the
template
and
actually
highly
cohesive
because
they're
template
generates
html
the
browser
parses
the
html
into
dom
nodes
then
your
display
logic
just
manipulates
dom
nodes
thing
they're
both
rendering
the
ui
to
separating
those
out
we're
set
technology's
not
concerns
and
the
technologies
that
we're
separating
are
deliberately
underpowered
so
i'm
going
javascript
templating
solution
and
it's
basically
copying
and
pasting
in
this
relying
on
kind
of
flow
control
deliberately
underpowered
so
there
are
abstractions
on
the
web
today
today
javascript
so
angular
is
hugely
javascript
part
of
angular
and
i've
highlighted
all
of
the
new
concepts
that
controllers
you
think
of
your
coupled
with
other
components
and
so
javascript
rather
than
relying
on
a
crippled
templating
language
to
do
it
components
and
build
components
out
of
other
components
and
finally
i've
highlighted
expressivity
so
you
can
shouldn't
have
to
jump
through
hoops
to
takeaways
are
that
components
are
reusable
and
they're
composable
and
they're
unit
testable
because
they're
so
if
you're
used
to
building
templates
spaghetti
code
so
we're
not
advocating
of
your
data
table
rendering
code
that's
display
logic
and
components
we're
all
specifically
cross-site
scripting
vulnerabilities
so
one
of
the
main
advantages
of
templates
early
on
was
strings
and
generating
markup
and
might
accidentally
concatenate
a
user-provided
variable
and
that
might
steals
someone
else's
cookies
and
then
strings
of
markup
with
react
we
have
a
automatically
escapes
everything
for
you
don't
want
to
do
this
they're
really
working
on
html
mock-ups
but
they
don't
four
hours
tweaking
the
box-shadow
called
jsx
let's
use
an
html
like
syntax
of
it
like
this
the
accessibility
of
templates
and
the
power
of
javascript
powerful
javascript
abstractions
that
programming
you
want
all
right
so
i've
that's
rerender
entire
application
on
there's
a
lot
of
variables
and
a
lot
of
heterogeneous
environments
is
is
also
geared
to
master
static
relations
and
evolving
in
time
are
relatively
poorly
inputs
and
we
can
look
at
the
outputs
them
look
like
item
potent
functions
reactive
programming
so
if
we
like
turn
item
to
my
to-do
list
I
didn't
have
to
page
conceptually
it's
really
simple
to
components
are
just
item
potent
we
declaratively
say
hey
this
render
look
like
and
it
doesn't
say
here's
the
is
declarative
everything
is
declarative
can't
do
this
to
the
real
browser
dom
we
can't
be
rerender
so
what
we
did
is
we
enemy
at
this
xyz
coordinate
at
this
which
generates
opengl
operations
and
flushes
those
to
the
graphics
card
make
here's
reacts
architecture
we
have
browser
you
know
clicks
or
key
presses
react
components
that
you've
described
than
opengl
operations
to
a
graphics
performant
and
one
of
the
real
thrashing
so
i'm
not
sure
if
this
is
there's
there's
a
couple
great
blog
measurements
for
you
and
then
if
you
optimizes
globally
for
your
application
show
you
a
little
video
demonstrating
and
rendering
and
flushing
every
single
requestanimationframe
which
means
that
10
milliseconds
I
want
to
point
out
that
there's
not
a
single
css
animation
or
virtual
dom
diff
and
rendering
so
I
don't
really
use
powerpoint
that
much
nav
remember
there's
no
css
animations
we're
actually
animating
two
content
areas
one
that's
that's
blurred
and
one
frosted
glass
overlay
effect
and
we're
doing
um
kind
of
some
3d
transforms
declarative
style
so
it's
not
like
oh
high-performance
so
we
can't
use
you
now
is
called
them
isomorphic
javascript
if
they
see
googlebot
they'll
render
which
is
a
headless
version
of
webkit
lot
it's
just
booting
up
a
dom
for
every
interactions
and
that's
what
what
react
I
don't
need
to
generate
any
dom
nodes
I
too
so
since
you're
not
rendering
to
a
dom
you're
rendering
to
a
virtual
dom
and
the
things
that
you're
rendering
our
optimizations
based
on
how
your
navigates
you
from
say
your
timeline
or
newsfeed
sorry
from
you're
building
with
components
not
were
talking
about
modular
components
don't
have
to
do
like
a
selenium
or
webdriver
kind
of
setup
to
get
that
that
colleague
sebastian
who's
sitting
over
virtual
dom
not
a
browser
dom
so
we
can
the
dom
primitives
so
you
can
use
react
same
interactive
charts
or
graphics
that
visualization
or
something
just
one
serialize
the
browser
events
from
the
ui
browser
interactions
i've
talked
about
build
components
not
templates
rerender
don't
mutate
the
it's
it's
a
little
bit
unwieldy
so
when
components
that's
a
great
question
so
web
components
is
a
big
constantly
composability
so
really
really
deep
components
and
I
don't
think
that
historically
web
components
has
been
focusing
on
that
aspect
and
there's
a
additionally
web
components
is
a
bunch
embraces
the
dom
and
adds
new
api's
don't
think
that
web
components
has
solved
the
problem
of
rendering
on
the
between
brenda's
so
like
css
animations
some
transitions
between
dom
States
if
the
page
like
you
have
a
jquery
plug-in
have
a
set
of
lifecycle
hooks
that
on
the
page
and
there's
a
dom
node

相關影片

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

加入好友

其他人正在學習的單字

1. cut
2024-05-10 19:08
2. opened
2024-05-10 19:08
3. arm
2024-05-10 19:08
4. in
2024-05-10 19:08
5. man
2024-05-10 19:08
6. refresh
2024-05-10 19:08
7. unless
2024-05-10 19:08
8. human
2024-05-10 19:08
9. graphic
2024-05-10 19:08
10. aunt
2024-05-10 19:08
11. offer
2024-05-10 19:08
12. stands
2024-05-10 19:08
13. against
2024-05-10 19:08
14. knock
2024-05-10 19:08
15. until
2024-05-10 19:08

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜