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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

Christoph Martens: JavaScript Level 9000 | JSConf EU 2014
觀看次數：308
some
linux
stuff
so
I
was
also
implementing
fixes
for
the
radeon
driver
or
fixing
or
supporting
or
ps
4
Basically
i'm
currently
focusing
on
sdl
stuff
so
my
new
runtime
is
based
on
nodejs
and
using
primitives
are
the
basic
understandings
of
data
types
and
in
javascript
it's
a
bit
complicated
So
in
these
examples
the
primitives
are
like
Numbers
Boolean
null
and
undefined
they're
primitives
and
defined
as
primitives
strings
and
Regular
expressions
are
not
because
they
The
strings
are
primarily
handled
in
the
runtime
memory
which
means
they
are
deallocated
after
arrays
and
Objects
are
basically
all
Object
instances
even
the
literals
"
{}"
For
closed
and
destructed
to
doubles
that's
the
so‑called
unboxing
it
then
has
to
be
unboxed
converted
and
boxed
again
something
like
dot
0
130
and
370
and
then
it's
still
handled
as
an
un/signed
integer
null
-
so
it
has numeric
value
-
you
can
add
it
to
other
strings
or
Numbers
and
it
and
prototypes
are
vector"
will
of
course
be
true
But
the
prototype
lookup
__proto__
which
is
a
non-standard
behaviour
for
looking
up
the
Prototype
Hierarchy
upwards
will
point
to
vector
Then
__proto____proto__
an
instance
of
Function
The
__proto____proto____proto
lookup
will
be
null
then
the
prototype
chain
is
over
and
the
jit
knows
there's
no
inheritance
level
upwards
from
a
Function
then
the
direct
__proto__
lookup
will
point
to
the
functionprototype
vectors
and
stuff
like
that
i'm
implementing
a
basic
Entity
and
I
want
to
reuse
the
vector
to
have
it
fully
integrated
with
the
javascript
vm
If
i'm
just
pointing
the
entityprototype
to
the
vector
itself
it
will
point
to
the
vectorprototype
you
get
the
correct
behaviour
with
the
"instanceof"
operator
and
closures
are
not
easy
to
backtrace
when
it
comes
to
memory
optimizations
let's
get
of
the
Global
scope's
foo
It
behaves
like
that
because
it's
not
referencing
to
the
original
foo
it's
always
referencing
to
the
"state"
of
foo
when
the
method
was
called
That
also
Next
Topic
closures
The
runtime
Memory
consists
of
primitives
they're
cleared
directly
after
your
Scope
like
Object
instances
but
they're
still
treated
as
runtime
allocations
inside
the
vm
They
are
basically
primitives
while
they're
not
able
to
use
it
if
you're
not
referencing
it
It
contains
Function
instances
Object
instances
and
assigning
a
new
Object
to
it
afterwards
var
foo
=
{}
foo
=
{}
That
means
unreferenced
Object
instances
always
create
Garbage
and
unreferenced
variables
it's
not
usable
at
all
One
of
the
algorithms
is
a
depth-first
the
other
a
breadth-first
search
Both
of
them
and
then
try
to
determine
where's
a
back-reference
The
breadth-first
search
algorithm
will
go
language
is
only
a
pointer
or
a
number
if
it's
optimized
or
basically
the
primitives
and
the
Hidden
classes
are
the
so‑called
abstractions
for
that
phases
is
reference-able
from
each
Root
node
of
the
instances
Then
you
cause
Memory
fragmentation
fragmentation
means
Memory
is
free
at
this
So
there's
so‑called
compaction
going
on
that
is
trying
to
re‑order
all
the
Object
that
are
so-called
handles
inside
a
jit
compiler
it's
basically
in
the
vm
something
like
a
will
use
later
after
the
compaction
and
resorting
and
if
they're
still
referenceble
or
not
by
the
copying
Garbage
Collector
algorithm
*yay*
30
seconds
left

相關影片

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

加入好友

其他人正在學習的單字

1. have
2024-05-03 04:35
2. introduced
2024-05-03 04:35
3. turn
2024-05-03 04:34
4. situation
2024-05-03 04:34
5. ten
2024-05-03 04:34
6. who
2024-05-03 04:34
7. husband
2024-05-03 04:34
8. plains
2024-05-03 04:34
9. bloom
2024-05-03 04:34
10. linking
2024-05-03 04:34
11. assuming
2024-05-03 04:34
12. description
2024-05-03 04:34
13. none
2024-05-03 04:34
14. going
2024-05-03 04:34
15. hesitation
2024-05-03 04:34

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜