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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

Aligning Paradigms Across Client and Server(less) - Jeffrey Hoffer - JSConf US 2018
觀看次數：467
okay
so
there's
there
she's
thought
stressing
now
mine's
more
like
an
align
programming
paradigms
across
about
a
new
way
of
programming
to
align
towel
programming
paradigm
and
it
has
derives
its
name
from
an
acronym
for
the
messaging
that
specifies
the
action
or
whereas
most
messaging
systems
or
most
messaging
we're
used
to
this
subject
is
two-dimensional
view
so
the
towel
model
mechanisms
one
is
an
async
attachment
so
that
we
can
explicitly
create
out-of-band
side-effects
as
well
as
an
intercept
interface
no
matter
whether
you're
is
currently
implemented
in
javascript
three
packages
on
npm
published
the
core
turn
components
into
towel
handlers
as
I
can't
see
an
optometrist
and
not
crack
importing
our
wire
tau
j
s
to
suck
at
koa
server
attaching
a
socket
io
for
handlers
that
we
need
to
occur
on
our
have
spaces
and
phrases
within
those
go
find
the
spaces
if
there's
no
spaces
or
it'll
return
it'll
find
one
series
of
handlers
that
will
occur
as
handler
for
when
somebody
enters
the
app
it's
my
fault
for
commenting
out
things
okay
cole
you're
back
in
actually
i'm
something
I
didn't
what's
that
yeah
process
of
bootstrapping
and
rendering
async
handler
for
that
so
we
don't
block
show
the
listview
reactor
components
that
are
exported
along
with
the
adapter
the
adapter
we
component
handlers
we
set
i'll
use
we
don't
have
to
keep
repeating
those
editable
state
within
it
but
it's
it's
client-side
as
well
as
the
server-side
state
of
entropy
over
time
so
I
don't
could
just
embrace
the
entropy
that's
entropy
the
tight
coupling
scaling
an
interview
in
2005
erich
gamma
one
of
interfaces
defining
the
vocabulary
of
tight
coupling
and
elaborating
on
eric's
these
abstractions
and
interfaces
we
domain-driven
design
can
help
us
to
find
mesthri
strings
to
represent
a
possible
they've
subscribed
to
so
they
just
wait
defining
interfaces
that
abstract
of
choose
a
message
driven
paradigm
by
scale
and
they're
deeply
embedded
and
we
need
to
decouple
scalability
from
our
object-oriented
class
in
the
reading
in
that
implementations
written
dated
from
user
interface
designs
long
ago
with
the
concept
of
unidirectional
data
flow
and
development
the
dao
embraces
unidirectional
data
flow
in
that
execution
environments
standardization
across
frameworks
there's
no
standardization
of
extension
intercept
async
and
inline
if
you
notice
gives
us
a
way
to
deterministically
they're
added
to
the
system
dynamically
entropy
occurs
when
our
product
managers
programming
is
a
paradigm
that
allows
a
logging
most
aop
implementations
provide
compilation
to
inject
code
but
they're
generally
focused
on
binaries
and
single
cross-cutting
concerns
handled
entropy
let's
see
some
examples
of
leveraging
couches
to
add
our
add
to
our
it's
still
responding
to
these
events
so
we
had
our
inline
handler
for
space
intercept
handler
for
space
find
that's
prevent
any
downstream
any
downstream
we'll
simply
add
it
at
an
async
handler
globally
to
anything
that's
stored
and
all
the
commenting
but
i'll
go
ahead
and
so
if
we
have
in
redis
we've
got
our
je
we
see
in
our
logging
cache
hit
that's
adding
a
wild-card
handler
as
an
stored
in
our
cache
we'll
have
a
cache
hit
embracing
the
entropy
inherent
in
our
systems
it's
completely
composable
and
aspect-oriented
programming
system-wide
trigrams
it
provides
a
ubiquitous
domain-driven
design
that
we
get
to
use
with
our
non-technical
and
our
product
decorators
testing
and
debugging
tools
url
paths
middleware
and
adapters
for
different
front-end
components
wrappers
seamless
as
well
as
implementations
we're
dealing
with
various
entropy

相關影片

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

加入好友

其他人正在學習的單字

1. giant
2024-04-29 10:30
2. out
2024-04-29 10:30
3. string
2024-04-29 10:30
4. billion
2024-04-29 10:30
5. wrote
2024-04-29 10:30
6. heythe
2024-04-29 10:30
7. spaghetti
2024-04-29 10:30
8. becoming
2024-04-29 10:30
9. discount
2024-04-29 10:30
10. multiplicity
2024-04-29 10:30
11. good
2024-04-29 10:30
12. find
2024-04-29 10:30
13. help
2024-04-29 10:30
14. apart
2024-04-29 10:30
15. flavor
2024-04-29 10:29

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜