Cheating Decline: Acting Now to Let You Program Well for a Really Long Time
Recorded at:
- Share
-
- |
Read later
Reading List

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.
Re: Yikes
by
Brian Marick
Thanks
by
Justin Forder
Re: Yikes
by
Dumitru P
There is obviously room for improvement, for example: after 7-8 minutes of discussing about how Crickets hear and mate, you admit this has nothing to do with the subject of the talk.
We might be doing things differently here in Europe, but I learned how we estimate distance and how we hear from my math and my biology teachers in school. This was when I learned in biology class why vultures have front facing eyes and hens have eyes on the opposite side (hint: some animals are hunters and some are prey) and also when I learned what sin()/cos() functions are. All these examples bring nothing new in general and, especially, nothing to the subject you are adressing.
The talk is, perhaps, just a basic introduction to evolutionary biology and natural selection and has little to do with IT in general, except for the two buzzword-compliant slides about TDD and Refactorings.
Re: Yikes
by
j bs
I rather found this talk refreshing, honest and interesting.
Re: Yikes
by
Dumitru P
I would not object so much to how interesting the presented facts are, as to how they can be applied to the subject being adressed. I was expecting to get some insight on how one can still work as a developer when he/she is 50-60 years old. Perhaps you could share a short list of practical advice you got from this talk.
Re: Yikes
by
burkhard kloss
...or "How to automatically manage complexity"
by
Bobby Norton
Brian uses crickets, baseball, tango, valet parking, chess, medical diagnosis, and XP to explore the appeal of automatic, complex behavior. He alludes to Daniel Kahneman's Thinking Fast and Slow in discussing the effortful vs. the automatic systems in the brain.
The implication is that, to the extent that you can make aspects of your job as a programmer automatic, you can use less energy to accomplish a task than those who have not. Effortful activity is tiring and error prone. Automatic activity is not tiring and is mostly accurate.
Brian offers some principles to help manage complexity:
* Constrain possible perceptions
* Make perceptions one-to-one with actions
* Convert goals to achieve into invariants to maintain
* Convert effortful calculation into automatic perception
* Make changes to simplify perception
For those of you interested in these topics, I think you'll enjoy spending an hour of your time here to get a glimpse of the neuroscience behind expert performance, whether those 'experts' are crickets, doctors, or programmers. If these ideas are new to you, good...the science of complex systems is full of examples of patterns in many seemingly unrelated fields operating off of similar principles and mathematics.
My advice: Get used to it. The complexity of the world is increasing. It's your job as a programmer to manage that complexity. Enjoy the ride!
Re: Yikes
by
Giorgio Sironi
Hello stranger!
You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think