It feels odd to look something up in the Cocoa-dev archive, and find that the answer has been sitting there for years, posited by persons whose names are no longer familiar. It leaves me wondering where they went; and what they’re doing now. And with a feeling of gratitude for their contribution to this technical ore. We have strong tools for mining those high value veins, today.
November 29, 2006
November 18, 2006
Every bug is like a murder mystery.
You begin to suspect everyone,
but that never stops your program from crashing.
Still, if you could only recognize that sliver
of laughter you hear as the bits crumble …
Of course, the sound manager
is always one of the first casualities,
leaving you in the dark.
It’s too bad you can’t just skip to the end
to reveal the answer, like in a book.
That would be a bit déclassé,
But you’d sleep much better.
November 15, 2006
The prototype seemed to work, so I took the plunge and overhauled my project. It was either gutsy or foolish of me, depending on how you look at it, but I’m debugging now, after spending several hours looking for a link problem. (The answer was staring me in the face all along.) And I’m having fun again, but things were a bit scary at times 🙂
November 14, 2006
For decisions and revisions which a minute will reverse.
I’ve decided to refactor the architecture of my project to take advantage of one of Apple’s core technologies. It’s Tiger or better, but there’s too much leverage to be ignored. I’ve done a partial proof of concept and now need to quickly do a prototype to be sure.
November 8, 2006
Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime.
Today on Cocoa-dev, Erik Buck, one of the senior Cocoa developers, answered a question in a Socratic tone: Eric’s reply informed the person who’d asked the question how to answer it himself. In doing so, Eric also provided a useful lesson to those of us just getting into Cocoa. Thanks, Eric!
“Usually, the easiest bugs to correct are the ones that predictably crash an application. You can easily look at the debugger stack trace to determine what went wrong.”
“That’s a good reason to use the assertion macros in your code. They’ll cause crashes to occur close to the problem, where they’ll be easier to understand, instead of later.”