Hopper fishing + picnic + chocolate cake from IGA = the best day of the summer!
Elly and Tova also came (they took the pictures).
Today I went with Elly to do some errands and get coffee (my main motivation for going). One of the errands was stopping at the thrift store, which, she promised, had tons of cool stuff. I spent about ten minutes browsing through some old clothes, but didn't really find anything that moved me until I got to the books. It is amazing how many mystery and romance books people buy and then throw away. What's more amazing is what I found among all those old Danielle Steele and Patricia Cornwell paperbacks:
Pretty sweet, eh? This thing has to be about 30 or 40 years old, and it's signed by the author, Chuck Jonkel, a famous bear researcher and founder of the Great Bear Foundation.
The best part: it was only $0.10.
But now I've discovered a way to read my ebooks that makes the experience tolerable.
My friend Jeff has been preaching the gospel of paperless books to me for almost a decade, but I've resisted for a long time. Now that I live in a place where it takes a few hours to just get to Borders and search for a tech book, I've started to cave. When I need a new tech book, I buy only the e-book. It's environmentally better, since all of the info will be outdated in six months anyway. Besides, it's not like I want to have a study full of classic web application books. Buying paperless books means I'm doing my reading mostly in Apple's Preview application.
The Bug Happy Fun Thing I found that has made reading tolerable in Preview is the Note Annotation tool.
It lets me make little notes of my thoughts as I read something. With tech books, this is great, because there are a million and one things that I read but then forget, or can't find again without searching for 20 minutes. Now, if I see something in a book I want to blog about later, or use in a project, I just add a note. When I'm ready to use whatever interesting page in the ebook that I've "Note'd", then I just view all Notes in the sidebar. No searching.
It's all about the little things.
Dave pointed me to the announcement about IE8's standards mode this morning. The short of it is that the IE team will do The Right Thing with version 8, rendering in IE8 standards mode by default, not IE7 standards mode, which can still be explicitly requested via meta tags. See the A List Apart article for how to do that.
I have two questions. First, why did anyone ever think it was a good idea to make IE7 Standards mode the default in IE8? I know all of the technical reasons and backwards compatibility blah blah blah, but when is a new version allowed to be a new damned version already? Second, why do they have Peter Boyle from Young Frankenstein at the podium on their Interoperability Page? I know I can't be the first to draw that comparison, but the resemblance seems particularly striking in this shot. Oh, and third, why is the name of that image file "hero.jpg"?
The Netflix Watch Instantly feature is pretty cool. There are a bunch of interesting documentaries, some good foreign films, and loads of kids shows on there (including Doggy Poo). Since we have decided to see how long we can hold out before paying for cable or satellite TV, I thought I'd ease the pain a bit by rigging up a Watch Instantly setup for our TV. Here's how I did it.
First, I already had an old PC with a Radeon 7000 in it. So I had RCA video out. I also had a sound card. I needed the two cables: one RCA video cable to go from the video card to the VCR or TV, and the sound card-to-RCA splitter cable. This has a headphone-like plug on one end (for the sound card) and the red-white RCA cables for left and right audio on the other end. I plugged these from the computer into the VCR, because it was more accessible.
Next, I had to get network to this box. I was so tired of wireless dropping out when the neighbor microwaved their popcorn or whatever that I actually wired Cat5 to my entertainment center. Once that was working, I verified I could play the netflix movies on the TV. I set my resolution down to 800x600 to be truer to the TV's 648x486 or whatever it is. If I had a decent TV, I could have left it at a more readable resolution I'm sure.
The final step was finding some way to control the PC so that I could browse movies and select the one I wanted to play. Reading text on the TV was extremely difficult, so I wanted a better screen.
I realized that since Elly always has her laptop going, I could just set up VNC between that and the TV's PC. The laptop would be a really big, but versatile, remote control. So that's what I did. RealVNC on the PC and Chicken of the VNC on the laptop. It works like a charm:
It's tricky learning design, especially as a developer. And I'm not talking about the aesthetic stuff--for some developers that may be downright impossible--I mean the technical world of HTML and CSS. The problem I've had over the years is that, as a developer, most CSS/HTML information on the web is not targeted at someone with my background. If you're like me, then you have a BS degree in computer science or engineering from a university where you were made to sit and think about everything from processor pipelines to XOR gates to compiler optimization to how much wood could a wood chuck chuck if a wood chuck could chuck wood and what would be the complexity of said wood-chucking in big-O notation, thank you very much, here is your degree, now go learn Java or Xt or MFC or whatever in the real world on your own.
So you know enough to write the CSS parser and rendering engine, at least on a theoretical level. But that won't help you to use it. Nor will it help you to know the quirks of the several rendering engines out there in the real world.
So I find myself in this quandary of knowing too much for my own good when I sit down to learn about CSS/HTML. Then I get impatient. I want the articles targeted at design-people to just cut to the chase. Stop talking about "If you wanted to have these pretty flowers in the upper left corner, you would float DIV x and put a background..." Show me the money. I'm not an art major. My web pages may suffer for that, but I can understand the box model if you would just tell it to me already.
The purpose of me writing this post, then, is to collect a few choice resources I've discovered in my own haphazard and unofficial CSS/HTML career.
Find a good CSS reset to start from ground zero. My philosophy is to know as little as I need to about the difference between browsers. The less you fill your brain with that meaningless crap, the more room you have up there for knowledge that might actually enrich your existence. One way to cut down on the browser-difference arcana in your head is by never using the default styles, which vary from browser to browser. You can choose from many of the reset CSS recipes out there:
Don't using clearing elements. I used break tags (BR) with a style of "clear: both;" for a long time to clear floats. Even though it is the W3C-recommended approach, clearing floats in this way will drive you crazy. (It is difficult, if not impossible, to get those clearing elements to share a uniform height across browsers.) I use Tony Aslett's clearfix method personally, although Dave pointed this out to me. It is a more recent technique, but I'm a bit hesitant to start using overflow to achieve clearing. It gives me scrollbar nightmares.
Understand the Holly Hack. I never understood the difference between clearing floats in IE and other browers until a I read an explanation about why the Holly Hack fixes it. I wish I had read this years ago.
Use Chris Pederick's Web Developer Toolbar. This is the single most awesome CSS tool that I use. The Edit CSS and View Style Information tools are almost all I need. Occasionally I will drop into Firebug when the View Style Information tool doesn't do the trick (it doesn't show the inherited styles as well as Firebug).
Don't take on IE6 without CSSVista. If you're like most people, you develop everything in Firefox or Safari first, then drop into the depths of hell to work out whatever is broken on IE6. One nice tool that lets you interactively edit CSS in IE and FF at the same time is CSSVista. It's free. It's not perfect, but it's the best I've seen for IE yet. The IE Developer Toolbar is also nice to have.
Don't buy reference books. It's funny how many CSS reference books there are. Same with HTML. You don't need me to tell you that these are a waste of paper, including that green paper that is your money. But there are some good CSS books that discuss layout techniques and browser bugs. It is definitely worth having one of these. I like this one a lot. It is also good to have a CSS cookbook on hand when you need to remember the right way to do some common CSS task. I use the CSS Anthology from time to time.
Read this book. For all of us who are not graphic design majors, who didn't know all those fancy terms in that documentary on Helvetica, I recommend The Non-Designer's Design Book. Nothing has helped me more in grasping the basic aesthetic principles of laying out a page. If you have to do anything with design, even if it's just laying out your church bulletin, you should read this book. It's short, easy, and will have you making passable designs in one day.
If you are a dev who has been designing for a while, this is probably all old hat to you. But if you're like I was a couple years ago (clueless), then an hour spent reading the links above will hopefully be a great starting point for you.
Birds I've seen in the past few weeks as the direct result of owning a dog and walking it in the early morning/evening:
These are only the ones I can identify. I have seen many others that I can only describe as "little brown bird in the grass" or "big black bird with white neckline" or "mini black duck."
Other wildlife that we've observed and/or barked at:
I just got forwarded an article by Hank Williams from a client who has been watching the ongoing Twitter scalability rumpus that has kept us entertained for literally years now. Blaine's recent point about scalability is one I would mostly agree with, and one which I'm sure he's tired of making. I haven't really been following the Twitter-talk on all of the techie blogs, except through hearsay. "Did you hear that TechCrunch said Twitter is dumping Rails?" "Did you see that post about Twitter scaling?" Yada yada yada. Half of it is inaccurate the moment it is posted, and the other half is fraught with misunderstanding and wild speculation.
One of the reasons I've been loath to follow these discussions is underlined by William's concession at the end of his post that, indeed, Twitter's scaling challenge is a "hard ... problem that requires a very specialized ... architecture." Aren't they all? And so that is why I don't read the pseudo-tech jibba-jabba of TechCrunch and others about the scalability of Rails in general based on the experience of one very unique site. Scalability is unique to each site. Indeed, you are a unique site when you have to worry about scalability. That means you are getting lots of traffic, and probably making money. Most sites don't make it that far.
But I didn't write this post to join the Rails scalability rant. I just wanted to mention one observation that I haven't heard yet in the Rails scalability discussion. Here it is: the web is a moving target, and the current discussion often fails to acknowledge that. The web today is demanding more of frameworks, languages, developers, and system architectures. For instance, on MOG, we knew scaling would be a major problem from the get-go because a central piece of the application involved hundreds of thousands of agents running on users' disks, reporting tens of thousands of songs. What website was doing that in 1997? For what piece of software are those numbers not a scalability issue? It's the same with Twitter (as Hank points out): millions of people tweeting all at once, very frequently, via web, phone, Facebook apps--who knows, maybe there's even a Twitter client for your hair dryer or coffee maker now. This sort of challenge is (relatively) new for the web. And new ones like it are being invented every day. The target is constantly moving and changing shape.
If we nailed down the goalposts of web scalability, no one would bother posting and trolling and debating about Rails scalability. It would be solved by a handful of good engineers in a couple of weeks. For good. But what would be the fun in that? You'd never hear about another site that does something you wouldn't think possible 5 years ago. And, as an engineer, you'd never have the fun of solving new scalability challenges to support those new sites.
I'm a huge fan of poetry. I didn't use to be. Ode on a Grecian Urn somehow failed to move me as an 11th grade English student. At least, it failed to move me to the point that I considered poetry an art form worthy of my attention. It was an arcane distraction for lonely English teachers, as far as I was concerned.
But then I had a kid. And I was unable to finish more than two pages of anything without being interrupted to change a diaper or play My Little Pony. This was a tough spot to be in, since failing to finish a book is somewhat of a moral issue for me. I can't explain that really--it just is. I don't have this problem with movies. I can walk out of a stupid movie without blinking. Maybe I have less respect for film as an art (and maybe that's because it so rarely takes the form of art). But whatever the reason, the fact is I hate to see a book on my shelf that I could not finish.
So what to do... I had been spending a lot of time in Borders and Barnes and Noble, mostly because there was not much else to do with the one hour in between dinner and bedtime, and, as I hope you already know, these book stores have Thomas the Train tables in the kids section. Word up to that. One day, while Tova was crashing trains off bridges, I wandered over to the poetry section. I started reading, and immediately I was hooked. I finished reading like five poems in as many minutes. This was progress on a grand scale for someone who hadn't been able to finish a book for three years. I think I left with Seamus Heaney's Opened Ground that night. It was a great discovery.
Since that fateful night in the bookstore, I've become a veritable poetry whore, subscribing to Poetry magazine, exploring new poets at the price of $20 per visit to Borders, and even scribbling out my own sorry verse when I have time. Like Ronald McDonald, I'm lovin' it.
Now that I'm out of the closet, I wanted to share one of my latest favorite poets, Wisława Szymborska. She is a Nobel Prize winner and a Pole. Just like another literary hero of mine. I bought her "Poems New and Collected" a few months ago, and I've been slowly savoring it a few pages at a time. A few days ago I came across a poem called "Census." Citing the many layers of ruins at Troy, she is talking about the ever-growing mass of humanity in history, and how we become part of it. That one-sentence intro does not do it justice; you should really buy the book to read the whole thing. Anyway, this is my favorite part:
We pass each other once for all time in department stores
shopping for a new pitcher.
Homer is working in the census bureau.
No one knows what he does in his spare time.
So far, I am really loving the Garmin Communicator Plugin. It is one of the best applications of a browser plugin that I have ever encountered. I suppose any browser plugin that allows you to pretend your browser is a desktop application is a great browser plugin. That's what I like best about the Garmin Communicator, anyway. You can plug your Garmin device in via USB, then sit back and let some free web application do its thing with your data. No download-upload nonsense.
Here's a little sample of how I'm using it in WalkingBoss (not live yet):
Things have finally calmed down a bit here. We're moved in to our new home, my office is set up, and I'm no longer looking for rogue printers to smash.
What's new? Well, I bought a house, got a dog, and moved. All pretty much within a month or two of elapsed time. I feel about 20 years older after doing all of that, but the calendar tells me that I've really only lost two months. Plus however much time you lose from eating 30 Filet-o-Fish sandwiches in as many days due to not having any of your kitchen stuff to cook with. Probably shaved about six months off my life there.
I've been on Facebook a bit lately, mostly for work. I don't really like Facebook, but on the plus side I've located a bunch of old friends. It's a bit weird how the internet enables you to keep track of your friends without really having to keep in touch with them. I mean, there's the usual "Hey, you're still alive, that's great!" conversation that seems part of the "friending" ritual. But beyond that, Facebook seems to be just a glorified address book for me. I know my friend Dave sees a lot of potential in Facebook, so I haven't completely ruled it out as another fad yet. But it will be a while before I'm really sold on it, as a user. As a technical person, of course I see the huge advantages it provides as an application delivery platform. As a regular person, I don't know if I'd still be a Facebook user if my job did not require it.
Our new dog is proving to be a great addition to the family. We found her at the animal shelter in Belgrade a week after we moved here. She is a Karelian Bear Dog, a breed with which I have been enamored since first reading about how they are being used to help with problem bears at the Wind River Bear Institute. When Elly looked on PetFinder and saw that a KBD was available, it seemed like a sign from above. We had both been joking prior to moving up here that I could own my very own bear dog, but I don't think either of us thought that it would happen so fast. For one, they're supposed to be super active and need some land to roam. Our tiny backyard would seem small to a Pomeranian, so I wasn't planning on getting a bear dog until we moved to a place with more acreage. But luckily for us, Sadie is an older dog who would rather lay around and squeak out dog farts all day in exchange for some chicken jerky treats. She's still a great dog, and she will play with you if you pretend to be a big vicious animal, but she is by no means chewing off our doorknobs or running off into the hills. In fact, just this morning she made me walk at about negative 1.5 mph up a hill back to our house in a windy snow squall because she was tired after our morning jaunt.
On the technical side, I'm continuing work on TravelersTable, while in my spare time trying to resuscitate WalkingBoss and develop a time-tracking module for the IDE I use (NetBeans). I've found that all of the dog-walking I'm doing has been good for my creative-technical side. The ideas come a lot easier when you're not stuck behind the LCD all day long. I'm considering getting back into ObjC or OCaml once I'm done with my other projects. I got an OCaml book for Christmas a year or two ago, and I never made it past the first chapter. Plus I've got some ideas about a WebKit app I want to build in ObjC. Too many ideas, too little time.
I guess today is tax day, as two people have already reminded me in their emails. I had forgotten because my taxes were done a bit earlier this year. The deadline for corporate returns is a month early, so I got all my stuff together for the accountant back in March. I'm pretty excited. I think this is the first year I will get a refund in about three years. It's not too much, but just knowing that the government won't take a big bite out of my hiney this month is a great feeling. For a couple years there, it seemed like any savings I built up were gone after April 15.
Speaking of money, I am totally amazed at the difference between Whole Foods and the local Town & Country supermarket here. I swear we pay 30% of what we did in Boulder. I do not understand cost of living at all. Dave told me he paid $13/lb for turkey at a Whole Foods in California while he was visiting family. Thirteen bucks for a pound. I think here it's like $4/lb or something. Of course, the comparison is a little skewed--I mean, it's not just cost of living differences when you compare a regular supermarket and Whole Foods. The Whole Foods turkey most likely spent part of its young life reading Plato, playing frisbee, and talking about social issues late into the night over some kind bud at a $40,000/year liberal arts college, so that figures into the $13/lb. But still. That's a huge difference.
5. Since you have no legs and are therefore not ambulatory, you can not get away if I decide to teach you a lesson.
4. I'm paranoid. After two consecutive paper jams I start to think you're just playing with me.
3. Underneath that gray plastic shell you have breakable parts, like...your scanner glass.
2. You are replaceable.
1. My Kung Fu Heel Hammer Kick.
I lost it today. I thought I'd give a little warning kick to this piece of crap when it jammed on me for the 8,023,235th time. I guess I kicked a little too hard because I heard the internals rattling around after my first kick and that set me off. Once I knew I had broken it, I got a little crazy and just kept kicking it. I guess movies really do inspire violence.
Elly and Tova came home just as I was vacuuming up the evidence. Elly asked, "What happened in here? Did you kill somebody?"
"Yeah, I did. I killed a printer today."
Elly took this a couple weeks ago during the eclipse:
...was looking off my back deck and seeing this:
Click on the image to see Elly's dog poo census.
This is one of those short articles that I post only when Google fails to turn up any useful information and I hope my solution will be helpful to others. If you are using the acts_as_taggable plugin in an older Rails project that you've recently come back to upgrade to Rails 2, you may find that you get an error like this one: NameError (undefined local variable or method `acts_as_taggable' for ...
I honestly don't know what changed, possibly the updates that were made to auto-loading constants (which I never really bothered to learn about), or maybe the difference is in my rubygems version. I'm not sure. Anyway, if you're seeing it, you can try putting this below your gem statement: require 'taggable'.
That fixed it for me, using Rails 2.0.2 and the acts_as_taggable gem version 2.0.2.