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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

End to End Apps with Polymer (Polymer Summit 2017)
觀看次數：357
reusable
user
interface
components
like
components
the
specs
were
designed
to
we've
also
shown
that
web
components
are
components
so
that's
why
i'm
going
to
in
a
nice
list
you'll
have
sorting
and
course
we're
going
to
have
a
responsive
to
target
it's
got
a
load
superfast
on
iteratively
to
deliver
a
great
user
experience
with
maintainable
code
that's
the
ui
so
it's
maintainable
and
reusable
internationalized
and
accessible
we
want
workflows
for
serving
and
debugging
and
good
news
is
there's
help
so
the
polymer
app
toolbox
we
launched
at
i/o
last
year
these
these
topics
so
the
polymer
cli
us
format
strings
in
our
polymer
templates
and
browsers
actually
now
have
good
cross-platform
support
for
formatting
numbers
and
dates
to
the
internationalization
API
the
paper
accessibility
our
app
layout
elements
idioms
responsive
layout
idioms
the
serve
built-in
support
for
web
components
components
polymer
lint
provides
a
polymer
build
gives
us
you
know
performs
a
lot
of
the
common
optimizations
that
for
how
you're
structuring
your
this
concept
of
server-side
renderings
newsletter
or
buy
a
product
or
bookmark
and
server-side
rendering
really
helps
it's
there
i've
got
this
throttle
down
not
to
say
that
server-side
rendering
is
server-side
web
components
on
the
server
focusing
on
the
right
metrics
and
for
a
good
time
to
interactive
is
this
don't
easy
enough
but
historically
it's
been
this
is
why
on
the
polymer
team
we've
decoupled
routes
that
can
all
fit
back
you
can
just
go
to
webpagetestorg
slash
pre-configured
for
testing
on
mobile
and
real
real
throttled
networks
metric
to
be
focusing
on
when
you're
budget
if
that's
what
we're
budgeting
translates
into
about
50
kilobytes
of
kilobytes
that's
a
good
rule
of
thumb
to
top-level
components
for
the
route
and
building
out
our
user
user
interface
so
then
factoring
those
drawing
boxes
to
leverage
reusable
components
wherever
our
go-to
source
for
javascript
go-to
source
for
a
reusable
web
reinvent
the
wheel
where
we
don't
have
not
just
for
our
useable
components
we
components
built
into
the
browser
like
I
importantly
our
components
aren't
locked
dom
to
encapsulate
the
rendering
really
we
want
without
losing
interoperability
thing
by
extending
polymer
element
our
and
we
can
do
that
incrementally
over
down
into
components
so
let's
just
focus
and
the
navigational
components
and
then
interactive
user
changes
to
a
detail
performance
factoring
the
ui
think
about
composing
and
coordinating
components
so
it
owns
them
and
it's
the
components
to
handle
user
interactions
that
sort
of
thing
mutating
some
data
and
propagating
that
components
add
ons
as
well
as
up
and
out
internally
while
still
communicating
in
web
components
org
things
that
you
composing
mediators
into
mediators
and
with
a
final
top-level
mediator
that's
mediating
other
components
and
you
can
there's
kind
of
a
trade-off
space
in
a
components
become
more
and
more
app
kind
of
more
generic
components
together
developer
workflows
that
we'll
see
there's
a
really
strong
ecosystem
that
of
add-ons
that
help
you
manage
async
terms
so
in
redux
the
global
mediator
trade-off
going
from
localized
state
management
where
it's
all
self-contained
we're
centralizing
where
all
the
actions
that's
logged
so
we
can
kind
of
have
a
dev
tools
are
snapshotting
that
global
callback
-
redux
to
get
the
in
any
state
point
out
is
that
if
you're
if
you're
--purple
--purple
concept
right
we
only
subclass
it
in
the
constructor
we're
redux
has
a
lot
of
extensibility
hooks
the
store
to
lazily
install
the
reducers
the
listings
reducer
is
responsible
for
make
sure
that
you're
importing
that
will
continue
experimenting
with
components
you
need
using
http
to
push
to
serve
granular
components
when
that
capabilities
of
the
browser
so
for
--purple
--purple
server
node
and
that's
outputs
that
come
out
of
the
polymer
that's
set
up
for
client-side
routing
that
can
automatically
detect
the
capabilities
of
the
browser
and
serve
browsers
that
don't
have
es6
we
can
for
the
capabilities
of
the
browser
and
we're
actually
integrating
purple
server
rendered
html
fully
rendered
html
that's
seo
and
social
snippet
generators
and
estate
json
so
that
I
didn't
get
sued
by
proof-of-concept
I
mean
I
feel
that
i'm
really
well
factored
ui
with
components

相關影片

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

加入好友

其他人正在學習的單字

1. he
2024-04-29 23:33
2. literally
2024-04-29 23:32
3. motherfuckers
2024-04-29 23:32
4. try
2024-04-29 23:32
5. marker
2024-04-29 23:32
6. splinter
2024-04-29 23:32
7. expand
2024-04-29 23:32
8. write
2024-04-29 23:32
9. outside
2024-04-29 23:32
10. party
2024-04-29 23:31
11. now
2024-04-29 23:31
12. guy
2024-04-29 23:31
13. good
2024-04-29 23:31
14. portion
2024-04-29 23:31
15. tell
2024-04-29 23:31

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜