Live data from Hacker News

Rich Hickey: "Simple Made Easy" from Strange Loop 2011 [video]

infoq.com

11–20 of 104 posts

Re: Rich Hickey: "Simple Made Easy" from Strange Loop 2011 [video]

#11
post #3

Ugh. Why don't they release the presos as opposed to having to deal with synchronous video?

This is my number one gripe about infoq. I love skimming slides to see if it's worth investing an hour in watching a talk.

Re: Rich Hickey: "Simple Made Easy" from Strange Loop 2011 [video]

#13
For me this was the best talk I've seen in a long while. It reminded me of how I felt when I first read PG's essays, someone articulating your own suspicions whilst going further and deeper and bringing you to a place of enlightenment and clarity.

BTW for those of you who haven't watched it, this talk is not Clojure specific.

Re: Rich Hickey: "Simple Made Easy" from Strange Loop 2011 [video]

#16
post #13

For me this was the best talk I've seen in a long while. It reminded me of how I felt when I first read PG's essays, someone articulating your own suspicions whilst going further and deeper and bringing you to a place of enlightenment and clarity. BTW for those of you who haven't watched it, this talk is not Clojure specific.

However it's a great advertisement for Clojure, since the set of things he highlights as enabling simplicity is pretty much a subset of Clojure (or included libraries, like core.logic).

I'd be interested in seeing someone present a different and convincing set of concepts. At this point, I think Rich has put together a very good toolset.

Re: Rich Hickey: "Simple Made Easy" from Strange Loop 2011 [video]

#17
post #4

A good talk. Leave it to a lisper though to call testing and type-checking "guardrail programming". Hickey says instead you should reason about your programming without acknowledging that testing and type-checking are ways to have executable documentation of your reasoning about your program. Testing does in fact feedback into complexity - if something is hard to test it may be due to complexity that you realize you…

Difficulty of writing a test can certainly be a complexity indicator, but in my experience the evidence is against testing having served this purpose very well to date, at least for the kinds of complexity addressed in this talk. If you look at around 31:27 in the talk, you will see ten complex things, with proposed simple alternatives. If testing helped people feel the pain of complexity and discover simple things,…

> fixtures, factories, testing lifecycle methods, mocks, stubs, matchers, code generators, monkey patching, special test environments, natural language DSLs

STOP STOP STOP! MAKE IT STOP!

This is the clearest indication of how (dogmatic) testing has become a vehicle that introduces complexity, rather than something that alleviates complexity.

Re: Rich Hickey: "Simple Made Easy" from Strange Loop 2011 [video]

#18
post #3

Ugh. Why don't they release the presos as opposed to having to deal with synchronous video?

I empathize, but at the same time, 5 min. of slide browsing would not drive the point home. People are trying to skimp when they should invest the time. Relax, reserve yourself an hour and enjoy the talk. This is a good one, and getting signals through sound, visual and text will leave a better imprint in our brains.

Re: Rich Hickey: "Simple Made Easy" from Strange Loop 2011 [video]

#20
post #4

A good talk. Leave it to a lisper though to call testing and type-checking "guardrail programming". Hickey says instead you should reason about your programming without acknowledging that testing and type-checking are ways to have executable documentation of your reasoning about your program. Testing does in fact feedback into complexity - if something is hard to test it may be due to complexity that you realize you…

He says relying on tests and type-checking to verify a program still does the right thing after making changes is "guardrail programming".

None of us do "guardrail driving", but we still put guardrails on roads.
Post reply on HN