Skip to content

Pecan Pie

Based on this recipe, but modified slightly. Super tasty; not too sweet and very nutty.

Prep Time: 15 Minutes
Cook Time: 40 Minutes
Ready In: 1 Hour 5 Minutes
Servings: 8

Ingredients

  • 1 Albertsons-brand premade Pie crust
  • 2 eggs
  • 1/2 cup butter
  • 1 cup light dark brown sugar
  • 1/4 cup white sugar
  • 1 tablespoon all-purpose flour
  • 1 tablespoon milk
  • 1.5 teaspoon Watkins double-strength vanilla extract
  • 1.5 cup chopped pecans

Directions

  1. Preheat oven to 400 degrees F
  2. In a large bowl, beat eggs until foamy, and stir in melted butter. Stir in the brown sugar, white sugar and the flour; mix well.
  3. Add the milk, vanilla and nuts.
  4. Pour into an unbaked 9-in pie shell. Bake in preheated oven for 10 minutes at 400 degrees.
  5. Reduce temperature to 350 degrees and bake for 30 to 40 minutes, or until done.
Tagged ,

Jobs at the Intersection

Walter Isaacson’s Steve Jobs is simply out too soon. The man died less than a month before the book hit the shelves, and the book has the feel of being rushed, with too much recitation and no enough reflection. But for all its failings, it’s worth reading.

Before we begin, let me caveat that I’m not going to talk much about the events of Steve’s life; the blogs are alight with people talking about all the juicy bits, and you can find that elsewhere. I am, instead, going to talk about the book qua book– how the book does its job as a biography and as a reading experience– and about the larger themes Steve’s life can tell us.

As a Biography

Let us begin with the parts it gets right. Isaacson had amazing access and Jobs’ blessing to talk to whomever he needed to, and he managed to do incredibly good interviews with a huge array of people. He compiled a ridiculous amount of information about Jobs’ life, and presents it clearly. He is brutally honest about how brutally unkind Jobs could be. It is a tribute to him that he manages to keep that objectivity even after he had become as close to Jobs as the end of the book would imply, and a tribute to Jobs that he wanted no part in whitewashing what would obviously be a somewhat unflattering biography. The prose is smart and clear and clean, with a few slips into being too-clever-by-half.

But the book falls far too often into chasing the end of the chapter. The story of Steve’s life is told as it was experienced, demo after demo, launch after launch, leave after leave. The chronology is important, but it is the first and simplest step in a biography, and for large tracts toward the end of the book we get nothing more than the chronology. Whereas Steve’s early life is told with a pop-psychologist’s eye toward motivations and internal conflicts, the last decade of Steve’s life runs by with nary a thought about it. You repeatedly get the feeling that Steve’s death came earlier than the publisher expected, and the last few drafted chapters had a quick copy-edit before being sent off to the printer’s.

The book also has some bizarre blind spots. Pixar is a perpetual second fiddle to Apple, which seems to have genuinely been the case but is never addressed directly. NeXT exists as a vaguely-defined wilderness that Steve wanders through during his exile, but its products are barely mentioned and what made them interesting, failures, and ultimately a successful foundation for Apple’s rebirth is never touched on. This contrasts especially oddly with the lovingly detailed story of the Mac team, which is taken nearly wholesale from Revolution in the Valley (Odder still: Andy Hertzfeld’s book is basically a love story to the rest of the team, but in Isaacson’s book every Mac-team story is told from Andy’s eyes, and so it seems Steve and he made the entire computer themselves). There are also huge industry movements that get nary a mention: the Internet isn’t ever important except to give an i to the iMac, and Job’s embrace of and slow distancing from DRM is never mentioned at all. Those two in particular are important for Jobs’ story: they tell of a platform nobody owns as a contrast to the many Apple created and curated, and the tools used for that curation and why they were abandoned.

Both the Internet and DRM share one thing in common with lots of other things given short shrift in the book: software is only ever important because it talks to hardware. This fits the “integrated system” that Jobs embraced and a theme that Isaacson emphasizes, but Steve being painfully obsessive over hardware was no different than his being painfully obsessive about the design of software, and there were a lot more software releases over the years than hardware ones.

The rushing and the blind spots combine to make it harder for Isaacson to present us with big-picture thinking about why Steve’s particular obsessions worked well for him. We hear a lot about painting the back sides of fences and owning the whole widget, which are important lessons, but they’re just supporting points of the real lesson. Let me build up to what that lesson is.

Lessons

The book does a very good job of painting how hard it must have been to be around Steve: he could be mean, he was driven, he often seemed arbitrary, and he didn’t care if you liked him. But between that you can see a deeper truth: it seems like it must have been incredibly hard to be Steve. Everything around him sucked all the time. No one around him cared as much as they should. No one “got it”, even when it was obvious, and even when Steve told them. The world was full of bozos who made crappy products, and Steve had to deal with both all the time. He was literally being annoyed by this stuff on his deathbed.

And that’s because being in tune with the design of everything around him was who he was, and he couldn’t turn that off. A continuing theme was mentors of Steve approaching him and telling him he was being a jerk, and Steve admitting it, promising to be better, failing to do so, and then saying that it was just “who he was”. He couldn’t turn off his design sense, and he couldn’t turn off his reaction when that sense was offended.

So as a defense mechanism he took Alan Kay’s words to heart, and invented the future. But Steve wasn’t the one to do the inventing, so we see a continuing string of people executing on his ideas. The interplay between ideas and execution is an important part of Steve’s life, but Isaacson doesn’t seem to notice the succession of pairings through the years:

In each case Jobs provides the impetus but someone else provides the technical expertise to make it happen. Jobs, though, was not just an “ideas man” who threw things over the fence: he was deeply involved in every aspect of the creation until the consumer swiped a credit card and took the thing home. His gift was knowing what would make the thing better, and his curse was an absolute inability to be shy about letting you know. So he found people who could take his criticism and use it as it was meant to be: as a tool to refine their craft.

Adding this all together, we see what made Steve great: he knew that every part of execution matters. This goes beyond the back side of the fence; it encompases his aversion to letting “B players” onto the team, and it fits with many people describing his ability to hone in on the weakest part of a design. It shows why he switched sides on DRM (avoid extra steps), and why he thought that integrated systems were superior (the seams always show). He knew and saw that letting a small fissure stay in a design could split the entire thing apart: Woody accidentally became a jerk, the bezel of the iPhone overshadowed the screen, the stores needed to focus on tasks not products. Products are holistic creations and must be thought of that way, or the stray threads are the first things that users will pull at.

Conclusion: Art and Technology

The basic pairing Steve came back to was art and technology. He told Isaacson this again and again, yet it falls behind the Reality Distortion Field in the book’s hierarchy of themes. But this was Jobs at his most self-aware: he saw that where he had done the best work of his life was when he found art and technology that matched, and where he could fuse them together. But a lot of times he missed the intersection: NeXT had art but the technology hadn’t caught up, yet. When the technology finally did catch up, the same art made Apple huge. In the same way, the technology of photorealistic 3D might some day make the Pixar Imaging Computer’s artistic dreams a consumer reality.

Spending so long searching for and living at that intersection meant that when everything starting to become a computer, balancing art and technology became an incredibly valuable skill. Apple suddenly had a head start on industries that they hadn’t even been in competition with a few years before, and that head start grew because most of their competitors weren’t even trying to find the balance.

Many are saying that Apple is Jobs’ greatest creation. I agree, but the measure of their greatness will be in how well they maintain the balance he created, and how successfully they continue to make technology that can truly be called art.

Tagged , ,

Computer Organization

On Oct 9, 2011, at 2:23 PM, Alejandro Duarte wrote:

I need help. On this computer (and every other I have ever owned) I am utterly disorganized.

Could you help me tame this beast of disaster, please?

I’m not sure how helpful I can be in this matter, but these are things that have helped me:

Use Dropbox

This gives you a synchronized files between multiple computers and mobile devices, simple archival system in the cloud (Website > Hover on file > Show versions), as well as allowing you to trivially share large files with other Dropbox users (with Shared Folders) and with the world (with the Public folder and right-click>Dropbox>get link). You’ve now got one tool that makes “getting the thing where I need it” much easier

Use nvAlt

This is a “shoebox app” where you shove everything you need to remember or keep track of, and it manages lots of text notes. I’ve got mine set up to store its notes in Dropbox (you can set that in Preferences) and come up with Control-Option-Space. I then use Elements on my iPhone to update things on the go.

Use Alfred

This allows you to find things on your computer faster: I bound mine to Apple-Space and replaced Spotlight. Now I can type application names, “find” and then some filename, people, math, etc. I also have a bevy of custom searches so I can find TV listings, D&D monsters, etc. My preferences for this are sync’d via Dropbox (sense a theme?)

Use TextExpander

This allows you to automate anything you type all the time. I put code snippets, markdown templates, file names, contact info, and lots more in here to allow myself to get things done quicker. Alfred has a “snippets” feature that’s somewhat similar but doesn’t auto-invoke. Snippets sync over dropbox, and there’s an iOS version that works in lots (but not all) apps.

Use 1Password

This helps keep track of your secrets. It’s mainly a Keychain replacement, but it also puts that information into your (you guessed it) Dropbox and (of course!) has an iOS app that means you have all that information at your fingertips whenever you need it. It also helps you break the terrible habit of using the same password on every site by making it easy to generate ridiculous passwords.

Use the Documents folder

If something is a text file it belongs in nvAlt; if it’s supposed to be accessible it goes in Dropbox; if it’s neither of those it goes in the Documents folder. Don’t put things on the Desktop; it’s where ideas go to die. If you must, put an alias on the Desktop to remind yourself about the thing. But if you can’t remember without that it’s not important enough to remember.

Use iCal

Put reminders and to-do items into iCal, with alarms, so that you’ll know what you’re supposed to be doing. I know a lot of people use OmniFocus or Things to other GTD apps, but I’ve never jumped onto that bus.

Keep Applications you install in /Users/yourusername/Applications

This is a tiny change in behavior that reminds you what parts of your computer are stock and which are custom; I have 16 things in there on my work machine, and each one is necessary on a regular basis. It’s too easy to lose things in /Applications and let old, useless apps sit around or useful apps be forgotten.

The general idea here is “keep everything in a place where you can find it easily later, and make as many of those places as possible sync to your other devices”. This is useful in its own right, but it also constrains you to put things where they’re “supposed to go” so that you invoke the power of the synching, and that makes it easier to find them and use them later on.

Missing Steve

Apple Front Page

Lots of people have already said how odd it has been processing the news of Steve Jobs’ passing: we didn’t know Steve and the vast majority of us have never even met him. And yet we grieve because he defined our industry is when it is at it’s best, and his example was what many of us have tried to follow.

He managed to take up so much of the horizon. He was the figure a lot of us wanted to be, the guy who saw further, knew faster, and made better. He strove to make the world a better place and succeeded beyond everyone’s wildest dreams except his own. Because as much as we didn’t know him everyone who did agrees that he was never satisfied, was always ready for the next step, and was always thinking about the step beyond that. That he won’t get to take those steps with us is one of the most hurtful parts of the whole thing: when he showed us what was next his smile let us all know how happy he was to have found it, but also how happy he was to be sharing.

I have no doubt that Apple will continue making outstanding products. But I will miss seeing Steve’s excitement, and knowing that there will always be one more thing.

Tagged

===

Who you are is a function of what you do; your actions determine your character because there is no other output of your character. People who do bad things are by definition bad people; people who do good things are good people. So being careful about what you do is really about being careful about who you are.

I’ve just gone through a two-month period of job searching with a resume that was very careful about laying out what I did because I didn’t want to be hired for a job I’ve done before and hated; I didn’t want to be the version of me who works on technology I am constantly annoyed by; I know who I am and want to be careful about it.

So while I can write Swing Applets, I’d really rather work on HTML5 apps; I can wrangle XAML but I’d prefer to be hitting up RESTful JSON services; I can write in whatever language you’re using but my favorites are Ruby, JavaScript, and Objective-C.

Those three languages are the ones I want to work with because those three are a part of my identity: their designs match my tastes and my philosophy, their communities are fun to engage with, and the web is aglow with interesting new things to do in them.

So when I landed a job last month doing Ruby on Rails development where we’d be doing green field development with the versions released a week prior, I was pretty near ecstatic. I could be the version of me that I’ve always wished paid the bills and actually pay the bills.

So it was quite a blow when, one week into the job, the world exploded. The tech stack we had been assembling was thrown aside and we were told we’d be doing Groovy on Grails instead (That the framework is named like a parody was salt into the wound). My tastes and philosophy were aghast at the JVM and its demands; the lack of community was staggering, and the web contained only years-old articles about uninteresting copies of even-older Rails features.

But the larger blow was the loss of identity: I went into work for a week happy to be doing what I was doing, and happy to get a chance to do what I’d wanted to do for years. Then, suddenly, I was just another Java programmer again; thrown into a world I had escaped five years before. Worse, I went from being a confident Senior Engineer to being a very opinionated novice.

One week more has gone by, and the room has stopped spinning. I’ve picked up enough Groovy and Grails to feel confident that we can make our deadlines, but not enough that I’m satisfied with my understanding of anything. Finding the clever parts of a new language and framework is always fun, and I’ve had moments of appreciation in the past week, but if I had my druthers I would switch us back to Rails in a heartbeat.

But I don’t, so instead I’m trying to roll with the punches; this is not the situation I would have chosen to jump into but it’s the situation I’m in, and so it’s the one I’ll make the best of. Learning new corners of the industry is kind of my schtick, so I’m at home exploring documentation and writing test cases for obscure language features. But I miss the version of me that I got a glimpse of for a week– that guy leapt out of bed a lot easier, and found his flow quicker, and was obviously having a really good time. Maybe someday I’ll find him again. Because I thought he was pretty awesome.

The title of this piece is an incredibly geeky programming joke, for which I apologize.

Tagged ,

Against Software Patents

At the behest of the Free Software Foundation, I just sent this email to Bilski_Guidance@uspto.gov to express how bad an idea software patents are. If you agree, send a similar missive (or steal mine, or FSF’s):

Software should not be patentable, because software is math. Adding a computer to do that math is an obvious next step, and should not be rewarded with a patent. At the very least, software patents should require working code just like patents for devices require blueprints; when the patent expires the knowledge contained therein should enrich the community, both by making the algorithm public and by making it clear what is and is not patented. That the code works is vitally important; we have seen far too many patents for things impossible at patent time but lucrative later, which wrecks havoc in an industry as quick-moving as ours which often finds a seemingly trivial insight suddenly central to how everything works. The existing system of copious overbroad and ill-defined patents leads to the entire industry living in fear of a massive patent war, with everybody arming themselves with defensive patents and being overly cautious, with the result that we as a public lose out on innovative products. The USPTO can and should stop issuing software patents to put an end to this.
Tagged , , ,

Review: A Game of Thrones

There is a good book inside Game of Thrones—maybe even two—but they are buried underneath an avalanche of monotonous detail, with four interconnected plot lines fighting each other for attention and strangling each other for air.

The book tries to do too much and instead does too little. As the first part of an epic-scoped series, it attempts to set the stage of an entire world, telling the reader all about the politics and society of the world and failing utterly to make any of it interesting on a human level. The cast of characters includes some gems, to be sure—Tyrion and Jon and Arya are my favorites—but their stories feel like backgrounds for later tales, not tales in their own right. Martin has scorned one of the cardinal rules of writing—start in the middle—and ignored it to his great detriment.

Tyrion is the closest to a complete tale, an antiheroic rise from scorned younger brother to man in his own right. But his tale cannot stand on its own without the suspicion that Tyrion is an assassin and a scoundrel, and that suspicion is born of the other narrators being more sympathetic than he is. Jon is a close second for completeness, a Shakespearean play of a bastard son taking what is given him and trying to find out how much honor his station allows him, and where. But his internal drama is driven entirely by the events played out in the other plot lines; information that reaches him too late for him to do anything: if the reader learned those events when Jon did their import and impact would be considerably lessened. Arya is an interesting character whose story I expect to start sometime soon, but as of the end of the book she’s still seeking a conflict she can fight in instead of merely observe.

The other characters are more deeply problematic. Eddard is completely bland, a tragic hero who in the end fails to let his tragic trait take him to his grave. Sansa is a foil and little else. Catelyn is a narrator’s tool and a convenient traveling point of view. Bran is nearly interesting but then consigned to live out a boring life far from any of the action. Their inclusion serves the greater epic, but it just clogs the novel and makes reading it slower, spacing out the actually interesting points with filler material.

But I’m intentionally ignoring Dany. This odd inclusion is one of the above-mentioned novels embedded deep within Game of Thrones, struggling to survive on its own. But here, too, is an odd mismatch: Dany is interesting, and her personal arc is appropriately scoped for the beginning of an epic, and it even has a resolution to make the novel feel complete. But Dany’s surroundings are completely boring. Martin conglomerates the Mongols and the Amerindians and the Huns into one confused people and then populated this nation with flat, uninteresting characters who cannot be distinguished from their cultural roles. Khal Drogo is the Dothraki, and the Dothraki are him: there is no distinguishing feature that allows him to be interesting, and when Dany falls madly in love with him the reader is stuck wondering why.

Now, it’s completely possible that the rest of the series takes all of these shattered shards of plot and hangs them onto one amazing chandelier, sparkling with Martin’s talent. And if the series was a trilogy I might even work up the courage to find out, but there’s already five books out and a sixth is on the way. I don’t want to spend the time to wade through more muck to get to the occasional interesting nugget.

And in the end, the scope is the problem. An epic is a fine and lofty goal, but if the component parts aren’t interesting enough to take me along for the ride, it’s a failure. And Game of Thrones’ meanderings from genuinely good ideas to regurgitated anglophilia lost me somewhere in its big mushy middle.

Tagged , , , ,

Balancing Budgets

Why do balanced budget proposals always make up their deficits with automatic spending cuts? Why couldn’t we have a system where the budget automatically adjusts taxes up to close the deficit in the previous year, unless Congress passed a 2/3rds vote to find appropriate cuts?

You’d have to watch out for Laffer Curve effects, because you’d get into a place where your raised taxes would actually make the deficit worse, but the aforementioned 2/3rds vote could take care of that.

The danger is that this year’s Congress would spend like a sailor and let next year’s Congress deal with the aftermath. But you spend like a sailor in order to keep your job, so you’d be in next year’s Congress!

An example. Let’s say you had a massive recession and this year’s budget was, say, $1.5 trillion in the hole. At the end of the year, CBO and/or JCT would take that number, adjust for inflation, population growth, and new interest due to the deficit spending, and determine that (for example) we need $1.7 trillion more in revenue. They’d split that into the various tax brackets (or a VAT, if we had one), and raise all rates across the board (or proportionally, or whatever) so that tax receipts next year should be $1.7 trillion more.

Now in a recession you don’t want to raise taxes, so Congress instead can pass a bill that’d find $1.7 trillion in cuts (again, as scored by CBO). If they only find $1 trillion in cuts, then taxes go up to cover the $.7 trillion that’s left. If they find $2 trillion in cuts, taxes go down. Congress has the final say, because that’s their job, but the default path is a budget balanced by bringing income into line with spending.

To take it a step further, this plan would require you to know how much extra revenue could be generated with various increases (which is kind of the opposite of what the CBO does now, but not dramatically different). With that information always available, you could just remove the need to pay for laws in the laws themselves, and just assume that they’ll be picked up in the next automatic stabilization. You might not want to do that all the time, but for the vast majority of things it’d be simpler.

Has any government tried this before?

Tagged ,

Beltway Rhapsody

(to the tune of Bohemian Rhapsody)

Inspired by this tweet from Dave Weigel


Is this the real news?
Is this just fantasy?
Caught in the cycle
No escape to reality
Open your eyes
Look up to the skies and see
I’m a swing voter (Poor boy)
I watch news on TV
Because I’m easy come, easy go
Polling high, polling low
Any way the wind blows
Doesn’t really matter to me, to me

Mama just saw a man
With a ballot in his hand
Pull a lever, take a stand.
Mama, the race has just begun
But now he’s gone and thrown it all away
Mama, ooh
Didn’t mean to make you cry
If I’ve not change my mind this time tomorrow
Carry on, carry on as if nothing really matters

It’s too late, Glenn Beck has come
Sends shivers down my spine
Mind is aching all the time
Goodbye, everybody
I’ve got to go
Gotta leave the truth behind and live the lie.
Mama, oooooooh (Anyway the wind blows)
I don’t want to choose
Sometimes wish I’d never been given the vote

[Guitar Solo]

I see a little silhouetto of a man
Ezra Klein! Ezra Klein! Will you do the Fandango?
Thunderbolt and lightning, very, very frightening me
(Yglesias) Yglesias (Yglesias) Yglesias, Yglesias Figaro
Politico-o-o-o-o
I’m just a voter nobody loves me
He’s just a voter from a rich family
Spare him his life from this monstrosity

Easy come, easy go, will you let me go?
Dave Weigel! No, we will not let you go
Let him go
Dave Weigel! We will not let you go
Let him go
Dave Weigel! We will not let you go
Let me go (Will not let you go)
Let me go (Will not let you go) (Never, never, never, never)
Let me go, o, o, o, o
No, no, no, no, no, no, no
(Oh mama mia, mama mia) Mama Mia, let me go
Conspiracy! Have the Palins put aside for me, for me, for me!?

So you think you can sway me with ads that are fly?
So you think I will love you for ads that you buy?
Oh, baby, can’t do this to me, baby
Just gotta get out, just gotta get right outta here

[Guitar Solo]
(Oooh yeah, Oooh yeah)

Nothing really matters
Anyone can see
Nothing really matters
Nothing really matters to me

Any way the wind blows…

Adobe InDesign CS2 and Migration Assistant

I installed Adobe InDesign CS2 on my last laptop about a month ago. CS2 is old; it came out in 2005 and runs under Rosetta, but it worked great on my MacBook Pro 2007 with its Core 2 Duo.

But that MacBook Pro was getting old, so work got me a shiny new one with an i7 inside. Nice! I used the Migration Assistant and pulled all my stuff over from backup, and was off and computing in no time.

But then yesterday I opened InDesign and it told me I had to reactivate. Stupid Adobe. I went through the motions and it denied me because I needed to deactivate the old machine. I pulled it out and did so. Now, trying to activate the new machine game me a useful error message:

Repair 93:-4

Oh, of course. That means… who has any idea what that means?

Google told me it meant “invalid serial number,” but since I was reading the serial number off the box I doubted that that was correct.

I tried the obvious things like a reinstall, an uninstall and a reinstall, reading the readme and doing all the things it told me to do to uninstall, then a reinstall, etc. No dice.

This was 2am, so I went to bed and in the morning I called Adobe Support. The tech was bright and chipper as he told me that CS2 wasn’t supported on Snow Leopard, but I could shell out $200 to get an upgrade to CS5. I was not amused.

So I started doing some more spelunking. I found a few more files to try deleting, but nothing seemed to help. Then I found an article on Adobe’s knowledge base that talked about setting permissions on /Library/Preferences/Adobe Systems/. I went over there and deleted the file entirely, relaunched, and activation went off without a hitch.

So if you’re seeing Repair 93:-4, just delete /Library/Preferences/Adobe Systems/ and relaunch; you should be good to go. If only their support line knew.

Tagged , , , ,