In this keynote talk from YUIConf 2011, Yahoo! JavaScript architect Douglas Crockford drops some science to explain why code style is important in programmin…
36 Comments on “Crockford on JavaScript – Section 8: Programming Style & Your Brain”
Comments are closed.
*Section 8: Programming Style and Your Brain*
*”That hardly ever happens.”*
is another way of saying “It happens.”
Crockford on JavaScript – Section 8: Programming Style & Your Brain
#javascript #video
#programming #style
I found this video highly interesting, and it’s not just about JavaScript,
but programming styles in general.
if (…)
{
}
*versus*
if (…) {
}
Great speaker and a very good lecture on your brain and programming.
YDN – JavaScript Programming Style & Your Branin
Need something to make your day better… Crockford on your Brain and
Javascript.
Check this video out on brain balancing. I highly recommend it.
I spent couple of hours watching this JavaScript series – and while it is
good in its entirety, should I recommend just a single part, this Section 8
would be it. It was definitely nice to get closer to JavaScript and to get
to know Douglas Crockford as well.
“We like to think that we spend most of our time power typing, I’m being
productive, I’m writing programs, but we don’t. We spend most of our time
looking into the abyss. Saying, my god, what have I done. How am I ever
going to make this work, and once we figure it out we forget that we did
all this.”
This is a great talk, even if you don’t use JavaScript. If you watch this
then please add a comment of what you think his main point was.
Interesting talk about programming style
This is a great talk for all programmers.
*Section 8: Programming Style and Your Brain*
#programming #style
I found this video highly interesting, and it’s not just about JavaScript,
but programming styles in general.
if (…)
{
}
*versus*
if (…) {
}
“This is not Java, this is a different language. Write in the language
you’re writing in. This is a different language; it has different rules,
different conventions, different good parts, and you need to respect that.
…
“I’ve thought for a long time if I could take a clean sheet of paper and
write a new language which corrects every defect in JavaScript but retains
all of the goodness in it — because there is a lot of goodness in it — I
would not have come up with anything like Dart. … It feels like it’s trying
go back and more Java-like.” – +Douglas Crockford, one of the great
ambassadors for programming in general and JavaScript especially.
Some pretty insightful stuff about the human brain and computer
programming.
And there is no reason to think that that should work.
New to Javascript? Or perhaps you have been writing it for a while but were
confused by strange syntax or behavior. Douglas Crockford, author of
Javascript The Good Parts, tries to highlight some of the great features of
Javascript as well as some of the more objectionable parts.
The overall focus of the talk is on the notion of code style and the
importance of style, not as a mechanism of self expression, but rather a
tool for imparting intent clearly even in a language that allows a great
degree of expression.
Watch it later
Only just seeing this now but really enjoyed it. 🙂
#javascript +Douglas Crockford #yui
Great video if you are a programmer or hope to become one.
Really nice talk on programming.
(JavaScript is just used as example.)
Very good =D
Very interesting and applies to much more than Javascript…
Wonderful speech! And the code style recommended is great too!
Clean up your JavaScript
Just finished watching +Douglas Crockford’s talk on programming styles. And
while I don’t agree with his proposed style in general, I do agree with
most of his ideas.
I’d also like seeing JavaScript get smaller. Some of the ES.next proposals
really creep me out because I always see them as highly unnecessary to be
included as syntatical abstractions directly in the language, exchanging
the ability of keeping the whole language at my head at any given time with
performance and user friendliness for edge cases, which could be covered by
libraries.
All in all, pretty nice (and funny) talk :3
EDIT: Oh yeah, my thoughts on code style is that showing intention and
structure is far more important than “reading as English” or anything. As
this, I’ve recently moved to using a LISP-inspired indentation and coding
style for JS. So far, I’ve found it rather easier to reason about what the
programs are doing, and the relationships between each statement and
expression :3
Good stuff!!
Excellent talk on programming style, JSLint, and the plight of the
Paleolithic programmer #javascript
Must Read!