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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

The Applied Science of Runtime Performance - Chrome Dev Summit 2014 (Paul Lewis)
觀看次數：326
everybody's
inaudible
of
runtime
performance--
and
by
runtime
where
I
talk
about
pixel
pipelines
and
architectures
seen
this--
it's
the
chrome
dev
Summit
site
I
won't
be
covering
the
nitty-gritty
details
You
can
find
it
at
csstriggerscom
it
triggers
in
the
browser
And
when
we're
building
fast-performing
sites
is
the
geometric
calculations
of
where
everything
And
basically
when
you've
got
a
reasonable-sized
dom
Go
into
the
devtools
go
to
timeline
or
whatever--
and
look
at
the
bars
into
pixel-rounded
kind
of
mode
which
I
think
it's
jarring
So
collectproperites--
it
takes
an
object
So
what
are
we
collecting
And
the
collectproperites
looks
like
this
which
I
get
through
this--
getboundingclientrect
which
Next
week
on
"esoteric
functions"
And
of
course
we've
let
the
browser
that's
right
we're
nice
and
composite-friendly
If
you
look
at
csstriggerscom
and
you
type
in
"transform"
it'll
go
compositor
that's
it
And
you're
right--
it
is
more
work
life
easier
for
developers"--
in
this
case
me--
let's
look
at
the
timeline
again
I
say
"in
the
middle"
because
the
eagle-eyed
amongst
i'm
an
artist"
You
can
say
archimedes
said
"use
will
change
sparingly"--
he
didn't
it's
true
it's
true
didn't
say
that
So
these
rules
that
we're
going
to
break--
they're
exceed
16
milliseconds
want
60
frames
a
second
One
second
divided
by
60
gives
us
16
milliseconds
or
clicks
on
something
we
actually
have
100
milliseconds
So
we've
got
100
milliseconds
that
we
bought
time-wise
The
animation
starts
notices
that
the
animation's
ended
stuff
or
the
toggling
of
classes
and
so
on--
that's
on
a
nexus
5
I
memorized
the
number
and
i've
got
some
freakish
talent
And
then
at
the
end
is
about
43-ish
milliseconds
So
we're
inside
that
window--
that
model
should
exceed
16
milliseconds
Why
wouldn't
you
paul
these
two
functions
Because
they
set
the
transforms
and
opacities
Now
because
of
the
way
browsers
optimize
boo-hoo
boo-hoo
triggers
that
tell
you
it
triggers
layouts
would
probably
firstly
i'm
only
doing
this
in
that
long-running
first
frame
The
100
milliseconds
that
I
have
as
a
window--
that's
write
read
write--
that's
causing
is
all
about
my
own
kind
of--
it's
quite
cathartic
Not
everything
is
jank-free
does
jank
i'll
do
it
slow-mo
and
just
bar
in
it's
also
bad
in
other
browsers
"clip"
triggers
paint
there--
it
doesn't
trigger
layout
So
on
non-chrome
browsers
it
always
causes
jank
On
chrome
and
android
it's
only
occasional
And
it's
better
when
there's
gpu
rasterization
switched
on
is
"never
sniff
the
user
agent
string"
don't
judge
me
don't
judge
me
The
card
javascript
file--
I
have
this
flag
in
it
and
it
says
run
lo-fi
animations
when
you
can't
cope
with
fast
clip
animations
Which
is
effectively
a
wrap-around
way
whether
it's
overflow
inaudible
like
animating
they
are
doing--
then
we're
going
firstly
I
think
it's
important
to
push
boundaries
grunting
and
push
i'm
a
bit
of
a
perfectionist
I
believe
it
will
get
significantly
better--
not
only
through
gpu
rasterization
in
chrome
headaches
i'm
kidding
of
course--
or
am
I
Because
it's
not
future-facing
so
I
of
related
to
the
whole
runtime
rendering
stuff
let's
talk
about
debugging
animations
for
a
second
it's
hard
isn't
it
there's
a
good
experimental
feature
speed
here
of
the
animations
and--
wait
We
know
that
debugging
animations
is
hard
The
site
will
run
when
you're
offline
it's
kind
of
a--
let's
call
it
inaudible
cache
replacement
it's
about
resilience
for
bad
wi-fi
and
fast
bootstrapping
of
the
site
I
think
historically
we've
been
in
a
situation
where
we've
been
very
network-bound
these
fast
bootstrapping
fast
launching
experiences
the
runtime
how
you're
doing
from
a
frame-specific
point
of
view
So
it's
OK
you've
got
devtools
timeline
and
that's
great
for
your
machine
This
is
the
w3c
repo
which
has
this
address--
w3c
frame-timing
and
it
has
a
cputime
Does
the
start
time
go
open
16
or
so
millisecond
intervals
If
I
have
a
cputime
of
near
60
milliseconds
So
with
the
compositor
thread
on
chrome
and
android
that's
where
the
painting
and
rasterization--
well
it
where
compositing
happens
that's
where
the
git
hub
repo
is
for
of
your
javascript
and
your
css
animations
the
side
navbar
doesn't
run
very
well
And
then
lastly
you
can
automate
The
new
person
joins
the
team
they're
well-meaning
So
frametime
api--
I
think
that's
really
exciting
I
wanted
to
mention--
it's
open
source
it's
not
bad
It
is
on
github
Google
chrome
dev
Summit
as
a
bit
of
a
tempter
for
definite--
it
was
worth
it

相關影片

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

加入好友

其他人正在學習的單字

1. company
2024-05-06 12:11
2. interaction
2024-05-06 12:11
3. its
2024-05-06 12:11
4. much
2024-05-06 12:11
5. before
2024-05-06 12:11
6. OK
2024-05-06 12:11
7. reclaim
2024-05-06 12:11
8. fast
2024-05-06 12:11
9. portion
2024-05-06 12:11
10. indeed
2024-05-06 12:11
11. serve
2024-05-06 12:11
12. teach
2024-05-06 12:11
13. repress
2024-05-06 12:10
14. alright
2024-05-06 12:10
15. attributes
2024-05-06 12:10

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜