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

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

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

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

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

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

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

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


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

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

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

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


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

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


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

Sarrah Vesselov: How to style in React and not lose friends | JSConf Iceland 2018
觀看次數：357
worked
at
a
small
tampa
startup
as
a
maintainable
css
architectures
the
team
proof-of-concept
looked
a
lot
like
a
traditional
mvc
architectures
to
a
more
stylescss
dependencies
and
inheritance
and
in
css
and
j/s
it's
really
a
css
and
jas
css
isn't
broken
you
just
javascript
to
create
css
reinventing
the
wheel
css
works
just
from
your
market
markup
the
cascade
is
the
basics
standardization
methods
otherwise
known
as
naming
things
intelligently
there
are
collision
by
lowering
specificity
and
encouraging
modularity
so
standardization
methods
work
with
css
sass
blast
standardization
the
css
camp
on
the
team
must
follow
the
syntax
religiously
so
in
here's
a
simple
component
folder
out
into
two
categories
we've
got
our
components
the
components
folder
represents
our
presentational
components
components
are
stateful
they
make
API
calls
etc
etc
there's
a
lot
of
benefits
concerned
with
the
presentational
there's
a
lot
of
pros
to
them
and
standardization
methods
in
general
I
components
there's
no
configuration
compiler
etc
so
configure
nothing
to
setup
and
put
together
using
bem
and
presentational
as
everyone's
following
that
syntax
rendering
engines
evaluate
css
selectors
are
some
cons
let's
face
it
naming
time
building
css
architectures
has
been
codebase
writing
something
that's
that's
to
look
at
preprocessors
we're
turning
this
into
that
so
css
preprocessor
takes
a
language
and
outputs
it
as
css
syntax
variables
operations
mix-ins
you
name
it
sass
or
any
preprocessor
is
that
you
example
i'm
continuing
to
use
the
bem
have
variables
in
here
and
there's
a
lot
separating
html
css
and
j/s
and
instead
we're
separating
based
on
presentational
components
and
container
components
and
outputting
to
an
individual
css
file
stylesheet
instead
so
pros
there's
a
lot
of
pros
to
pre-processors
sass
gives
you
the
power
obviously
of
variables
mix-ins
nestings
it's
got
a
lot
of
really
i've
seen
some
some
devs
new
to
sass
hell
there's
look
they're
like
10
deep
general
reduces
the
need
for
mix-ins
and
talk
about
inline
styles
and
inline
to
the
actual
dom
node
and
again
they're
maintainable
than
the
first
example
it's
this
was
not
scalable
the
font
size
and
color
palette
even
more
distressing
inline
Styles
and
css
and
jas
so
inline
Styles
only
supports
a
subset
of
css
css
generates
actual
css
and
we're
gonna
get
some
positives
to
them
inline
Styles
of
the
trump
card
and
specificity
right
there's
no
way
someone's
gonna
accidentally
override
them
or
leave
workarounds
to
address
media
queries
pseudo
selectors
all
of
the
things
that
cascade
so
you're
not
able
to
make
and
interestingly
enough
the
components
because
you're
placing
these
Styles
single
stylesheet
so
css
and
j/s
is
cons
that
were
plaguing
inline
js
could
I
think
it's
evolved
quite
a
bit
so
style
components
weren't
around
in
utilize
this
tag
tagged
template
see
we're
importing
styled
from
style
components
so
we're
using
that
we're
importing
that
library
and
then
we're
so
wrapper
equals
style
dot
section
in
inline
it's
actually
generating
a
css
we've
broken
it
down
is
we've
flexibility
and
scalability
long-term
as
around
to
construct
larger
components
presentational
components
they're
components
so
your
separate
separating
out
your
presentational
from
your
logic
style
components
actually
has
basic
sass
variables
nesting
mix-ins
there's
a
lot
glamour
style
components
aphrodite
css
relying
on
a
library
that's
the
hot
new
teams
have
designers
and
implementing
because
this
utilizes
so
much
of
what's
up
misunderstandings
and
foster
help
you
in
those
conversations
and
I
so
if
there's
a
mixture
of
skill
levels
designers
that
are
implementing
your
css
and
building
complex
styling
systems
to
accommodate
theming
and
reusability
make
live
separately
from
presentational
considerations
so
think
about
these
styling
decision
even
more
importantly
I
tension
and
defensiveness
before
conversations
even
get
started

相關影片

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

加入好友

其他人正在學習的單字

1. toughest
2024-05-04 05:20
2. world
2024-05-04 05:20
3. suffocate
2024-05-04 05:20
4. wore
2024-05-04 05:20
5. might
2024-05-04 05:19
6. me
2024-05-04 05:19
7. then
2024-05-04 05:19
8. connection
2024-05-04 05:19
9. back
2024-05-04 05:19
10. half
2024-05-04 05:19
11. inside
2024-05-04 05:19
12. people
2024-05-04 05:19
13. even
2024-05-04 05:19
14. cheese
2024-05-04 05:19
15. humans
2024-05-04 05:19

本月觀看影片單字排行榜

本月查閱單字排行榜

本月聆聽單字排行榜