David Brunton
Wednesday, June 27, 2007
Decoding the Universe
This book was a fun two-day read. No pretense at groundbreaking science- just a pleasant revisionist history of modern physics as if it has always been leading up to the inexorable conclusion:
Seife uses a lot of words like "grim" to describe this conclusion, which is a little annoying, but I still thought it was fun. ¶ 3:07 PM Links to this post
information is the basic building block of the universe.
Seife uses a lot of words like "grim" to describe this conclusion, which is a little annoying, but I still thought it was fun. ¶ 3:07 PM Links to this post
Tuesday, June 19, 2007
Cowboy Coder
I am probably the closest thing that you know to a real cowboy. I spent four years working for Dale Thiele on the Lazy TC Ranch outside Goldendale, WA. While I was working there, I learned a valuable lesson about being a "cowboy" (keep in mind that "cowboy" was always meant as an insult in that context):
Always Sit in the Middle
It's what cowboys do. The do it because in a pickup, there are only three choices- one is to drive, another is to open gates, and the third is to sit in the middle. And sleep. Because I was working back-breaking labor for 20-or-so hours a day, I learned quickly that the middle was worth fighting over. And that's why they called me a cowboy.
They, like programmers, considered it an insult.
Well, I'm a cowboy coder, too. Which means that I live for a single design pattern. It's not Object Oriented or Functional or Procedural or Imperative, and it won't be found in the Gang of Four or Chris Alexander. It applies to classes, objects, functions, procedures, routines, methods, accessors, variables, closures, and darn near every other kind of first-class member of a programming language:
¶ 3:20 PM
Links to this post
Always Sit in the Middle
It's what cowboys do. The do it because in a pickup, there are only three choices- one is to drive, another is to open gates, and the third is to sit in the middle. And sleep. Because I was working back-breaking labor for 20-or-so hours a day, I learned quickly that the middle was worth fighting over. And that's why they called me a cowboy.
They, like programmers, considered it an insult.
Well, I'm a cowboy coder, too. Which means that I live for a single design pattern. It's not Object Oriented or Functional or Procedural or Imperative, and it won't be found in the Gang of Four or Chris Alexander. It applies to classes, objects, functions, procedures, routines, methods, accessors, variables, closures, and darn near every other kind of first-class member of a programming language:
Take the Shortcut
The shortcut is the route that gets there first. It doesn't help you if you have to write more code (e.g. drive) or open and close gates (e.g. fix bugs).
What it means in practice is that while there are a large number of ways to implement a function that works (where "works" is defined fitting a spec or fulfilling a contract or doing what it's sposed to), the best one is the one that gets me taking a nap sooner, and woken up with dumb questions later.
I am a cowboy.
So there.
What it means in practice is that while there are a large number of ways to implement a function that works (where "works" is defined fitting a spec or fulfilling a contract or doing what it's sposed to), the best one is the one that gets me taking a nap sooner, and woken up with dumb questions later.
I am a cowboy.
So there.
