[busy signaL]
[Tuesday, August 30, 2005]
the reason why i haven't had time to do pretty much anything the past three days
episode 47 and counting.
sige ingat.ü
posted by stani at 2:24 AM
comments (1)
[Monday, August 22, 2005]
a series of unfortunate events
i. tuesday, august 9
two days before my band and i were going to perform a set for malate's annual reinkarnasyo ng salita, we were informed that a) we were prohibited from carting in full-sized amplifiers and thus electric instruments were out of the question, and b) since the other band [severo, i believe] had backed out because of this revelation, we now had to prepare two sets. naturally, this meant we had to scrap our playlist and draw up two new ones, but in addition, it also meant that i had to somehow get my hands on an acoustic bass.
ii. thursday, august 11
i had arranged to borrow said acoustic bass, but things went awry and i had to content myself with playing rhythm guitar. except that my my sister had made off with our guitar in the name of an oral presentation, and i had to make even more arrangements to ensure that i would be playing anything at all.
since we hadn't really practiced and our playlist wasn't that apt to begin with, we weren't really expecting a warm reception, although the fact that there was hardly any reception, warm or cool, was a tad disappointing. the reinkarnasyon isn't exactly a popular event, but there is that expectation that used seats would outnumber unused seats, however slightly. on the bright side, less audience members meant larger complementary dinner portions.
not content with what they'd served us, i dropped by a friend's condo for some sushi and chit-chat. on my way out a few hours later, i ran into the reinkarnasyon after-party crew, who were on their way in, and needless to say it was at least three or four more hours before i was sober enough to extricate myself from their company. the devil's own good timing, some would call it.
iii. saturday, august 13
not really so unfortunate, merely tedious: a jaunt to school to attend a lecture for bonus points in my philosophy class. when i say "attend" i of course mean "buy a ticket, sign attendance, and exit as quickly as is respectable". on my way back to gox, i chanced upon pogz, who was in the mood for a few rounds of lalabu. our guest of honor was paxi, who was so delighted by new-found love affair with alcohol that he decided to recreate chudor's duxmobile incident, but without the moving vehicle.
after leaving a series of territorial markings in the student's nook and under the agno benches, he decided to pass out on the stairwell underneath wow telenet. here we took a number of photographs which i now realize aren't flattering at all, so i won't be uploading them anytime soon. after a good hour or so of babysitting, we finally managed to bundle him into a taxi and the rest of us took a hard-earned dinner at jollibee, courtesy of nads, who was coincidentally celebrating his own happy birthday.
later that night, paxi sent a message thanking me for my concern, and assuring me that he was almost over his "food poisoning", as his mother put it.
right.
iv. monday, august 15
for reasons that defy all logic, sir cortel got married. i don't know what to make of that; i'd always assumed he'd remain a bachelor by necessity. i wonder what he was teaching the day he decided to propose - carpe diem, in his philosophy class? signs of the impending apocalypse, perhaps, in christian living? chaos theory, in physics? my take is, he wasn't teaching at all; he simply hit upon a joke that would finally, finally make someone laugh.
v. tuesday, august 16
jp and i had been toying awhile with the idea of forming a band together, and we finally decided to concretize the idea. this is purely fyi, since we're a long way from playing live, or even recording songs. first things first: we need a male vocalist and a drummer. any takers?
vi. friday, august 19
i had ordered a batch of hash brownies from timmy since i'd always been curious about them. i did not realize how long it actually took them to hit so, long story short, i ended up eating two entire squares. some three hours later, after dinner at home, i suddenly found myself rather high. at that time i was writing a two-page essay on prayer and discernment to be submitted via email by midnight. i honestly don't know what i wrote, and haven't yet read through it; the fact that i named the file "prayer and dizernment" isn't particularly motivating. i think that chudor [who partook of the brownies as well] was better able to illustrate the feeling at that moment:
chudor: woah... lahat ng kinakain ko feel na feel ko
self: munchies
chudor: sarap ng oreo!
chudor: parang ice cream na hindi
chudor: or ice cream na tinabunan ng cookies
chudor: ang lasa
chudor: woah!
chudor: meron pa akong isa pare...
chudor: na oreo
self: wtf chuds... blog na 'to
how unfortunate.
sige ingat.ü
posted by stani at 2:50 AM
comments (2)
[Monday, August 08, 2005]
x: lam mo ung ice cream na parang dila??
x: ung jelly tongue??
x: un ata un e
x: try mo kiskis sa itlog mo
x: feel ko ok un e
x: hehehe
self: putangina naman -_-;
clue: "boots of haste! gloves of masturbation!"
sige ingat.ü
posted by stani at 1:14 AM
comments (2)
x: ung jelly tongue??
x: un ata un e
x: try mo kiskis sa itlog mo
x: feel ko ok un e
x: hehehe
self: putangina naman -_-;
clue: "boots of haste! gloves of masturbation!"
sige ingat.ü
posted by stani at 1:14 AM
comments (2)
[Sunday, August 07, 2005]
strange how 'lucky' things are easily misplaced or destroyed unless one keeps an eye on them. perhaps they have a mind of their own, a wanderlust. or perhaps, a sense of duty. imagine this scenario:
whatever man creates artificially is inherently unnatural, and therefore chaotic by design. perhaps, then, in order for them to function, each must have in or near it an object of order, such as something beloved [recall how in the velveteen rabbit, the boy's love made the rabbit real, i.e.: natural]. therefore, once this object is removed, the thing containing or otherwise depending on it, breaks down.
how is this 'essence', if you will, selected? let's say it is the first favorite thing to touch the completed machination. then, you have buildings collapsing after a hundred-year-old frog escapes from its cornerstone; buses careening off the road after a conductor ejects a ball from out the last row of seats; guitar bridges flying off the body after a sticker is absentmindedly scratched off.
now imagine anima, feng shui, and metaterrorism.
sige ingat.ü
posted by stani at 12:44 AM
comments (0)
whatever man creates artificially is inherently unnatural, and therefore chaotic by design. perhaps, then, in order for them to function, each must have in or near it an object of order, such as something beloved [recall how in the velveteen rabbit, the boy's love made the rabbit real, i.e.: natural]. therefore, once this object is removed, the thing containing or otherwise depending on it, breaks down.
how is this 'essence', if you will, selected? let's say it is the first favorite thing to touch the completed machination. then, you have buildings collapsing after a hundred-year-old frog escapes from its cornerstone; buses careening off the road after a conductor ejects a ball from out the last row of seats; guitar bridges flying off the body after a sticker is absentmindedly scratched off.
now imagine anima, feng shui, and metaterrorism.
sige ingat.ü
posted by stani at 12:44 AM
comments (0)
[Thursday, August 04, 2005]
i see it but i don't believe it
how fare the ravens?
sige ingat.ü
posted by stani at 9:20 PM
comments (0)
[Wednesday, August 03, 2005]
now that i'm in a more relaxed frame of mind [and our grade has been set in ink], the grand adventure of our advandb machine project warrants a more thorough retelling:
the project consists of a 1700-line table of data with sample output, and a 100-line table of data whose output is to be predicted by a program capable of inferring cause and effect rules. this was an obviously daunting task so our group allowed ourselves an extra day just in case we hit snags, meaning we started two days before the deadline.
as i mentioned two posts ago, one group had finished their project ahead of time, and i managed to secure a copy of their source code. foolishly thinking that all we had to do was to create a shell of our own and use their engine to actually run the thing, we didn't bother to doublecheck if our assumptions were correct until 10pm of day one. in hindsight, the file size should have given us an important warning - their project was too complex for us to decipher in a day, let alone three hours [our original estimate].
we immediately relocated to the kitchen table with a ream of bond paper to plan our own system from scratch. the atmosphere was rather grim, since was scarcely enough time to implement the system if we were still on the design phase, not to mention that we were so jittery that the frequent distraction the television provided was more than welcome.
actual coding started at around 2am. around the same time, the aforementioned the day you said goodnight invasion reached its peak, even playing simultaneously on three different channels. equally persistent were jessica simpson's these boots (were made for walking) and brownman revival's cover of the eraserheads' maling akala [more on that later], but neither was as annoying in terms of quantity, even combined. miraculously, by the time the sun rose, we somehow had a user interface and a file input system.
we resumed work at 4pm the next day, and before midnight, we had our data storage system down pat. only two hurdles remained: the algorithm for predicting data, and the algorithm for displaying the results. we used the ide3 approach, which calls for the system to compare input and deduce a decision tree, which in layman's terms is a diagram wherein you start at the top and travel downwards, identifying which branch to take by refering to the input.
for example, the sample data:
red + small + round == apple;
green + small + round == apple;
orange + small + round == orange;
red + big + round == watermelon;
green + big + round == watermelon;
results in the following tree:
1. is it big or small? if big, it is a watermelon; if small, go to 2.
2. is it red, green, or orange? if red or green, it is an apple; if orange, it is an orange.
so if you have big + orange + round == ?, the system tells you that you have a watermelon, despite the unusual color. notice that the 'round' data item is never used, since it's not really helpful in qualifying data.
anyway, back to the story:
we figured that the bulk of the thinking had to go into finding a way for the computer to figure out which data were pertinent to forming the tree and which were not, and although we were right in that regard [we finished encoding the formula by 4am], we suddenly realized that we had no clue how to make the sytem use the tree, once we built it.
the funny thing was that so far, whenever a particularly nasty concept took more than an hour to implement, maling akala would play on some channel or the other and we'd figure it out within the next few minutes. chalk it up to coincidence, a harbringer of divine intervention, or a second wind brought on by blind faith, whatever it was, it was working. when our theory was proved yet again with the final solution to the tree conondrum, we started singing snatches of the song whenever stubborn errors were finally hammered out [usually through some intelligence-insulting means, such as adding a semicolon at the end of a line, or doubling an equal sign].
come monday, we were told that the morning batch of defenses had been cancelled in favor of a wednesday schedule. having selected 11am as our time, we naturally assumed that ours had been among those moved. since we had double-checked the veracity of the schedule change with another faculty member, it was some hours before we realized that some professors have a different definition of the time separating forenoon from after. luckily, we managed to convince "death prophet" that she had failed to make the distinction between morning and whatever the hell she called the hour before noon, and were given another slot.
during our defense, she instructed us to input the entire 1700 line sequence into the system. as we were using a laptop, the strain caused our program to crash, which she then blamed us for. this only served to remind me of the fiasco last year when she asked me to comment out all of the error handlers i'd wired into that subject's project, then deducted points when the system started displaying erroneous results given input she designed, which were well beyond the scope agreed upon for the subject. the difference was that this time, she further deducted 40 points for supposedly incomplete documentation.
but here's the kicker - guess what score we ended up with? 85. that means that if our documents had been complete and our program had run correctly, we would have gotten a total score of 145. how is this possible? because she pulls grades out of thin air. don't think that i'm gloating over this fact. far from it, since some groups i know that deserved high marks received borderline ones.
i would have thrown a grievance suit in her face a long time ago, if not for the risk it would pose to my scholarship. for those of you out there who know who i'm talking about, and don't particularly care about a 0.0 if it's for a good cause, i can provide you with more material, and paxi has pledged to carry out the paperwork.
otherwise, don't make the mistake of having her as a professor. and if you do, don't the mistake of assuring yourself that you'll pass, unless you have at least one chinese groupmate [did i mention that she's a lech?].
marami ang namamatay sa maling akala.
sige ingat.ü
posted by stani at 10:02 PM
comments (2)
the project consists of a 1700-line table of data with sample output, and a 100-line table of data whose output is to be predicted by a program capable of inferring cause and effect rules. this was an obviously daunting task so our group allowed ourselves an extra day just in case we hit snags, meaning we started two days before the deadline.
as i mentioned two posts ago, one group had finished their project ahead of time, and i managed to secure a copy of their source code. foolishly thinking that all we had to do was to create a shell of our own and use their engine to actually run the thing, we didn't bother to doublecheck if our assumptions were correct until 10pm of day one. in hindsight, the file size should have given us an important warning - their project was too complex for us to decipher in a day, let alone three hours [our original estimate].
we immediately relocated to the kitchen table with a ream of bond paper to plan our own system from scratch. the atmosphere was rather grim, since was scarcely enough time to implement the system if we were still on the design phase, not to mention that we were so jittery that the frequent distraction the television provided was more than welcome.
actual coding started at around 2am. around the same time, the aforementioned the day you said goodnight invasion reached its peak, even playing simultaneously on three different channels. equally persistent were jessica simpson's these boots (were made for walking) and brownman revival's cover of the eraserheads' maling akala [more on that later], but neither was as annoying in terms of quantity, even combined. miraculously, by the time the sun rose, we somehow had a user interface and a file input system.
we resumed work at 4pm the next day, and before midnight, we had our data storage system down pat. only two hurdles remained: the algorithm for predicting data, and the algorithm for displaying the results. we used the ide3 approach, which calls for the system to compare input and deduce a decision tree, which in layman's terms is a diagram wherein you start at the top and travel downwards, identifying which branch to take by refering to the input.
for example, the sample data:
red + small + round == apple;
green + small + round == apple;
orange + small + round == orange;
red + big + round == watermelon;
green + big + round == watermelon;
results in the following tree:
1. is it big or small? if big, it is a watermelon; if small, go to 2.
2. is it red, green, or orange? if red or green, it is an apple; if orange, it is an orange.
so if you have big + orange + round == ?, the system tells you that you have a watermelon, despite the unusual color. notice that the 'round' data item is never used, since it's not really helpful in qualifying data.
anyway, back to the story:
we figured that the bulk of the thinking had to go into finding a way for the computer to figure out which data were pertinent to forming the tree and which were not, and although we were right in that regard [we finished encoding the formula by 4am], we suddenly realized that we had no clue how to make the sytem use the tree, once we built it.
the funny thing was that so far, whenever a particularly nasty concept took more than an hour to implement, maling akala would play on some channel or the other and we'd figure it out within the next few minutes. chalk it up to coincidence, a harbringer of divine intervention, or a second wind brought on by blind faith, whatever it was, it was working. when our theory was proved yet again with the final solution to the tree conondrum, we started singing snatches of the song whenever stubborn errors were finally hammered out [usually through some intelligence-insulting means, such as adding a semicolon at the end of a line, or doubling an equal sign].
come monday, we were told that the morning batch of defenses had been cancelled in favor of a wednesday schedule. having selected 11am as our time, we naturally assumed that ours had been among those moved. since we had double-checked the veracity of the schedule change with another faculty member, it was some hours before we realized that some professors have a different definition of the time separating forenoon from after. luckily, we managed to convince "death prophet" that she had failed to make the distinction between morning and whatever the hell she called the hour before noon, and were given another slot.
during our defense, she instructed us to input the entire 1700 line sequence into the system. as we were using a laptop, the strain caused our program to crash, which she then blamed us for. this only served to remind me of the fiasco last year when she asked me to comment out all of the error handlers i'd wired into that subject's project, then deducted points when the system started displaying erroneous results given input she designed, which were well beyond the scope agreed upon for the subject. the difference was that this time, she further deducted 40 points for supposedly incomplete documentation.
but here's the kicker - guess what score we ended up with? 85. that means that if our documents had been complete and our program had run correctly, we would have gotten a total score of 145. how is this possible? because she pulls grades out of thin air. don't think that i'm gloating over this fact. far from it, since some groups i know that deserved high marks received borderline ones.
i would have thrown a grievance suit in her face a long time ago, if not for the risk it would pose to my scholarship. for those of you out there who know who i'm talking about, and don't particularly care about a 0.0 if it's for a good cause, i can provide you with more material, and paxi has pledged to carry out the paperwork.
otherwise, don't make the mistake of having her as a professor. and if you do, don't the mistake of assuring yourself that you'll pass, unless you have at least one chinese groupmate [did i mention that she's a lech?].
marami ang namamatay sa maling akala.
sige ingat.ü
posted by stani at 10:02 PM
comments (2)
trish: so.. whats up?
self: nothing much
self: writing for malate
trish: oooooh
trish: whats it about?
self: gayness
self: it's creative non-fiction
trish: ok
self: err... you haven't read my blog recently, have you?
self: i kinda came out
trish: sorry
self: it's ok
trish: what do you mean came out?
self: have you read my last entry?
trish: title
self: "brave new world"
trish: shit ano ba yan di ko makita
self: baka di ka nakalogin sa blogger? friends-only sya
trish: ay yun na yun
self: seen it na?
self: everything's spelled out there
trish: still cant see it MY GOD I HATE THIS
self: :D
self: what's your status?
trish: where?
self: your ym status i mean
trish: "i have vertigo, spin me"
self: does blogger have friends-only entries?
trish: i have no idea
self: it doesn't, fyi :P
self: i just took you for a little spin around you-wish land
trish: ok yay
trish: thank you
self: XD
trish: that made me smile thanks
self: wait... so you did wish it?
self: i hope not O_o
trish: hahahahaha
trish: im so gullible
self: omg you did >_<
self: how is one supposed to feel when his friends want him to be gay?
self: i feel kinda insulted
self: it's like
self: "oh i like you but i don't want to be your gf so just be gay so we can do lover-like stuff without me having to say we're together"
trish: thats called friends with benefits
trish: and no responsibility
self: easy for you to say. you're not the transgendered half T_T
sige ingat.ü
posted by stani at 1:30 PM
comments (3)
self: nothing much
self: writing for malate
trish: oooooh
trish: whats it about?
self: gayness
self: it's creative non-fiction
trish: ok
self: err... you haven't read my blog recently, have you?
self: i kinda came out
trish: sorry
self: it's ok
trish: what do you mean came out?
self: have you read my last entry?
trish: title
self: "brave new world"
trish: shit ano ba yan di ko makita
self: baka di ka nakalogin sa blogger? friends-only sya
trish: ay yun na yun
self: seen it na?
self: everything's spelled out there
trish: still cant see it MY GOD I HATE THIS
self: :D
self: what's your status?
trish: where?
self: your ym status i mean
trish: "i have vertigo, spin me"
self: does blogger have friends-only entries?
trish: i have no idea
self: it doesn't, fyi :P
self: i just took you for a little spin around you-wish land
trish: ok yay
trish: thank you
self: XD
trish: that made me smile thanks
self: wait... so you did wish it?
self: i hope not O_o
trish: hahahahaha
trish: im so gullible
self: omg you did >_<
self: how is one supposed to feel when his friends want him to be gay?
self: i feel kinda insulted
self: it's like
self: "oh i like you but i don't want to be your gf so just be gay so we can do lover-like stuff without me having to say we're together"
trish: thats called friends with benefits
trish: and no responsibility
self: easy for you to say. you're not the transgendered half T_T
sige ingat.ü
posted by stani at 1:30 PM
comments (3)
[Tuesday, August 02, 2005]
i would have updated sooner, but i'm one of those people who can't think when drunk, sleep-deprived, or both. i still have 22 hours to account for, so this entry mayn't be as detailed as some of you may wish.
i. wednesday
total sleep: 2 hours
started decent work on the machine project due for friday of that week. not so much coding as continuing to brainstorm, but since my groupmates for this project played a more active role in system design and execution than the ones i usually get, we achieved a lot nonetheless.
we started out on the wrong foot, actually, since i managed to come by source code of an already finished system. trusting too much in the reliability of this windfall, we wasted four hours playing super cosplay wars before venturing a look at what we were actually given. needless to say, we were let down and thus spent the rest of the night designing our own functions.
the video of hale's the day you said goodnight came out on one of the three music channels we were flipping between no less than 14 times that night. you can only laugh at a familiar face for so long before that too becomes another monotony to escape from. luckily, jessica simpson's new video was just as prolific.
ii. thursday
total sleep: 0 hours
hale was still going strong the second night in a row. it's a bad sign when you vehemently avoid a music video to the best of your abilities but only decrease run-intos by a minimal margin. all publicity is good publicity, except too much of it. and a shame, too - their bassist packs quite a wallop.
as for our project, we managed to finish it a good number of hours before the deadline, but only minimum requirements were accounted for. i appreciate neither the teacher nor the subject, so i was just relieved it was over with. just so long as she gives us a respectable grade, i'll be willing to hold my tongue.
iii. friday
total sleep: 6 hours
perhaps i should have taken a nap in the malate office before heading home. i lost about an hour anyway falling asleep in the jeep and having to backtrack all the way from baclaran to the south superhighway. more importantly, perhaps i should have resisted that bottle of beer, those three shots of brandy, that pitcher of vodka-pomelo, and those three more shots of brandy.
iv. saturday
total sleep: 6 hours
band practice went alright, considering my lack of recent practice, although i was late about half an hour due to the latest installment of my commuting adventures, this time involving the mrt and 15 minutes of unexpected walking. that experience probably won't be allowed a repeat, since the service we're receiving from our usual venue isn't worth the trouble of getting there. suggestions within the taft or mandaluyong areas will be appreciated.
i turned in early, but only managed to credit two hours of recharge before receiving an invitation to a midnight food trip. ah yes, where would we be without obscenely loud vibrating cellphones. my neighborhood friends and i, including chudor and james soon found ourselves thirty minutes after midnight in bf eating free tapsilog, but no part of that journey was stranger than the fact that one of my companions [mister as-seen-on-tv] had chosen to wear white pekpek shorts to the outing.
to round out the night's activities, gio [who arranged for said night's activities, if "neighborhood friends" was a bit vague] and i stopped by another gin-and-pulutan gathering, which i expected to leave presently, seeing as i knew only two in the group, and only gio well, at that. for better or worse, i ended up leaving well after the sun rose. a new group of friends? i'll know by next week's get-together.
v. sunday
total sleep: 6 hours
my plans to sleep until sunset were thwarted by my parents' best friend, who had lunch with us. i mentioned that malate was interested in a creative non-fiction account of my bicultural upbringing, and so most of the afternoon and evening was spent by me furiously taking down notes on family history for literary material. it's very promising, i assure you. perhaps by third term it'll be polished enough to warrant inclusion in the issue, in case you're interested.
and since it was sunday night, i remembered at the last minute that four documents were due the next day for our practicum subject. i debited another two hours quantifying and qualifying format and content with our ojt supervisor. not the most interesting way to lose sleep, but hey, it worked.
vii. monday
total sleep: 4 hours
thankfully, i had dota to blame for this, although our games wasn't particularly enjoyable. i've reached a point of next-to-no fervor for the game. if i wasn't a channel op, i'd probably cold turkey, but i think this apathy's largely due to our series of crushing defeats as a clan. i'll win a few first and then see what happens.
although not directly related to my lack of sleep for the day, monday too saw chudor, paco, ivan, and i trapped for a full 30 minutes under the awning of a now-defunct sari-sari store, vainly waiting for a sudden rainstorm to abate. actually, we got a good enough glimpse of the storm's extent while still safe and warm within the confines of the duxmobile, but the rains had subsided to a drizzle by the time we parted ways.
i expressed concern over the ominously clear skies, but chudor silenced me with a jin-esque* wave of his hand and those four fateful words: "we can outrun it!"
viii. tuesday
total sleep: indeterminate
i had not planned to go to school, but had to take care of some loose ends that someone else dropped on me unexpectedly. which brings me here, in the ccs faculty room, tying out a blog entry when i'm supposed to be churning out sample programs for next term's objectp classes. no surprise there, although what was surprising was how much time i spent browsing through wikipedia over the past few weeks instead of finishing my current story for malate, which is what i envisioned myself doing for a good portion of the allotted 30 hours.
as of today, i still have three hours left, which isn't enough to finish either deliverable. owel. it's not like i'm not used to losing sleep over my commitments.
sige ingat.ü
---
jin-esque : something that is inspiring to the point of foolhardiness. from the korean proper noun "jin" and the french suffix "-esque". id est, the words "we will challenge that definition!" as a reply to a professor questioning our capability to finish a masteral-level thesis within the standard time frame.
posted by stani at 4:39 PM
comments (0)
i. wednesday
total sleep: 2 hours
started decent work on the machine project due for friday of that week. not so much coding as continuing to brainstorm, but since my groupmates for this project played a more active role in system design and execution than the ones i usually get, we achieved a lot nonetheless.
we started out on the wrong foot, actually, since i managed to come by source code of an already finished system. trusting too much in the reliability of this windfall, we wasted four hours playing super cosplay wars before venturing a look at what we were actually given. needless to say, we were let down and thus spent the rest of the night designing our own functions.
the video of hale's the day you said goodnight came out on one of the three music channels we were flipping between no less than 14 times that night. you can only laugh at a familiar face for so long before that too becomes another monotony to escape from. luckily, jessica simpson's new video was just as prolific.
ii. thursday
total sleep: 0 hours
hale was still going strong the second night in a row. it's a bad sign when you vehemently avoid a music video to the best of your abilities but only decrease run-intos by a minimal margin. all publicity is good publicity, except too much of it. and a shame, too - their bassist packs quite a wallop.
as for our project, we managed to finish it a good number of hours before the deadline, but only minimum requirements were accounted for. i appreciate neither the teacher nor the subject, so i was just relieved it was over with. just so long as she gives us a respectable grade, i'll be willing to hold my tongue.
iii. friday
total sleep: 6 hours
perhaps i should have taken a nap in the malate office before heading home. i lost about an hour anyway falling asleep in the jeep and having to backtrack all the way from baclaran to the south superhighway. more importantly, perhaps i should have resisted that bottle of beer, those three shots of brandy, that pitcher of vodka-pomelo, and those three more shots of brandy.
iv. saturday
total sleep: 6 hours
band practice went alright, considering my lack of recent practice, although i was late about half an hour due to the latest installment of my commuting adventures, this time involving the mrt and 15 minutes of unexpected walking. that experience probably won't be allowed a repeat, since the service we're receiving from our usual venue isn't worth the trouble of getting there. suggestions within the taft or mandaluyong areas will be appreciated.
i turned in early, but only managed to credit two hours of recharge before receiving an invitation to a midnight food trip. ah yes, where would we be without obscenely loud vibrating cellphones. my neighborhood friends and i, including chudor and james soon found ourselves thirty minutes after midnight in bf eating free tapsilog, but no part of that journey was stranger than the fact that one of my companions [mister as-seen-on-tv] had chosen to wear white pekpek shorts to the outing.
to round out the night's activities, gio [who arranged for said night's activities, if "neighborhood friends" was a bit vague] and i stopped by another gin-and-pulutan gathering, which i expected to leave presently, seeing as i knew only two in the group, and only gio well, at that. for better or worse, i ended up leaving well after the sun rose. a new group of friends? i'll know by next week's get-together.
v. sunday
total sleep: 6 hours
my plans to sleep until sunset were thwarted by my parents' best friend, who had lunch with us. i mentioned that malate was interested in a creative non-fiction account of my bicultural upbringing, and so most of the afternoon and evening was spent by me furiously taking down notes on family history for literary material. it's very promising, i assure you. perhaps by third term it'll be polished enough to warrant inclusion in the issue, in case you're interested.
and since it was sunday night, i remembered at the last minute that four documents were due the next day for our practicum subject. i debited another two hours quantifying and qualifying format and content with our ojt supervisor. not the most interesting way to lose sleep, but hey, it worked.
vii. monday
total sleep: 4 hours
thankfully, i had dota to blame for this, although our games wasn't particularly enjoyable. i've reached a point of next-to-no fervor for the game. if i wasn't a channel op, i'd probably cold turkey, but i think this apathy's largely due to our series of crushing defeats as a clan. i'll win a few first and then see what happens.
although not directly related to my lack of sleep for the day, monday too saw chudor, paco, ivan, and i trapped for a full 30 minutes under the awning of a now-defunct sari-sari store, vainly waiting for a sudden rainstorm to abate. actually, we got a good enough glimpse of the storm's extent while still safe and warm within the confines of the duxmobile, but the rains had subsided to a drizzle by the time we parted ways.
i expressed concern over the ominously clear skies, but chudor silenced me with a jin-esque* wave of his hand and those four fateful words: "we can outrun it!"
viii. tuesday
total sleep: indeterminate
i had not planned to go to school, but had to take care of some loose ends that someone else dropped on me unexpectedly. which brings me here, in the ccs faculty room, tying out a blog entry when i'm supposed to be churning out sample programs for next term's objectp classes. no surprise there, although what was surprising was how much time i spent browsing through wikipedia over the past few weeks instead of finishing my current story for malate, which is what i envisioned myself doing for a good portion of the allotted 30 hours.
as of today, i still have three hours left, which isn't enough to finish either deliverable. owel. it's not like i'm not used to losing sleep over my commitments.
sige ingat.ü
---
jin-esque : something that is inspiring to the point of foolhardiness. from the korean proper noun "jin" and the french suffix "-esque". id est, the words "we will challenge that definition!" as a reply to a professor questioning our capability to finish a masteral-level thesis within the standard time frame.
posted by stani at 4:39 PM
comments (0)