|
8/19/00
The biggest bitch about writing castle rooms
so far has been learning to use the editor --
excuse me, the "developer interface" --
which is in a very primitive state. But I'm
picking it up, a little bit at a time, which I
find to be the best way for me to learn an editor
without overloading my brain and getting too
frustrated.
It helps that its creator is available to help
me with it. Yesterday I was trying to create a
room template and couldn't figure out how to get
rid of some code. I called up Pär at the office.
"How do I delete [chunk of code]?" I
asked.
"Um... you can't really. Heh, it's funny
you should focus on that little problem right off
the bat; Michael's been begging me to put that in
for months."
"For god's sake, I've got to have a
delete command!"
"I know. All right, I'll code one. Hey,
can you come get me and give me a ride home?"
"I'll come get you when you put in a
delete command."
"Okay!" He hung up.
A thought occurred to me. I hit redial and
reached his co-worker Eric.
"Hi, it's Karen. Can you pass along this
message to Pär: 'It must be a functioning
delete command.'"
"'Must be a functioning delete command',"
Eric repeated. "Got it."
"Thanks," I said, and hung up.
My phone rang about three minutes later.
"Delete is implemented," said Pär.
"Can you come get me?"
"What? Michael's been after you to do
this for months and it was a three-minute hack?"
"Hee hee! Well, I'm always busy with a
whole list of other things that need coding, you
know."
"Damn, do I get results or what!" I
crowed.
"Yep. You've also got more leverage than
Michael does."
I picked him up at the office.
|