News

My campaign to produce Shakespeare's Sonnets: A Graphic Novel Adaptation needs your help! Please sign up at https://www.patreon.com/fisherking for access to exclusive content and the opportunity to be a part of the magic!

I'm also producing a podcast discussing the sonnets, available on
industrial curiosity, itunes, spotify, stitcher, tunein and youtube!
For those who prefer reading to listening, the first 25 sonnets have been compiled into a book that is available now on Amazon and the Google Play store.

Saturday, August 19, 2023

bits and pieces

tuesday night:

i went to bed a little while after posting. about an hour later, i got paged. i was groggy as ****. i dragged myself out of bed, and began investigating.

an hour later, the alarms went back to normal and i still had absolutely no idea what had gone wrong. it was awesome.

wednesday:

it appears that i forgot to mention that on tuesday morning, i made a mistake when setting up a wire transfer order and rushed to the bank on the way to work to get it cancelled. as useless as my personal bankers always are, the manager handled the cancellation in two seconds between other clients and i was on my merry way.

on wednesday morning, i attempted to create the correct order and was mortified to see that i'd received the following message from my personal banker: "the instruction from yesterday was executed successfully". i scrambled to get back to the bank and try and fix it, only to have him apologize weakly that what he'd meant to say was that the instruction to cancel the order was executed successfully.

#@$!ing IDJIT.

i got into the office and immediately tried to work out what had gone wrong the night before, one of my coworkers gave me some tips and i learned that we have a constant test that failures are handled correctly, which fails when the failures aren't handled correctly. so if there aren't failures - which there weren't - then the tests (correctly) fail.

but why weren't there any failures?

because our tests use an external API that wasn't responding as expected. WHO THE #@!$ USES AN EXTERNAL API FOR PRODUCTION TESTING?!?!

it turned out that wasn't the only problem with this repo that hadn't been touched in months, and i ended up losing the entire day to eventually get the first part of a three-part fix deployed. then in the evening, when i got home, i realized that i hadn't  reviewed one of my coworkers PRs from the day before - i personally *hate* long turnaround times, so when he messaged me around 9pm asking if he should rather pass the review to someone else i felt even shittier. so there i was, wednesday night, reviewing code...

over dinner, we finished watching spider-man: across the spider-verse. i actually do have a very serious complaint about the movie: *SPOILER ALERT* it doesn't have an ending. WTAF?!!

yesterday:

"no, no! i didn't mean for you to do it on your home time!"

sure. anyway, at least it got done and i still felt / feel a bit bad about the delay.

i finally got the wire transfer order right, and was very pleased to see the money arrive in my canadian account within a couple of hours - that still amazes me.

thursday felt like a bit of a wreck. i worked from home, what i got done took much longer than anticipated and was quite frustrating. i also joined gd and mr smear for an emergency grocery shopping run in the intense heat. i worked at an outside table while waiting for them to need me to carry bags, because all the inside tables with air-conditioning were occupied.

i felt quite faint when we finally returned home from carrying heavy bags in the heat.

we had just enough time to cool off a bit before i took mr smear to his jiujitsu class, where i worked while he trained. we did have an incident on the way, i feel like i handled it pretty well but i don't know if he really *got* the message...

afterwards, i took him to see his therapist and worked from the coffee shop next door. at least the allegedly-vegan chocolate ball and delicious iced-tea made that a good experience.

today:

i woke up around 2/3am sweating and uncomfortable. it must have taken me anywhere between half an hour to an hour to finally get up and put air-conditioning on in our bedrooms. in the morning, gd informed me that that's what's been happening the previous days as well, only she was bothered before i woke up.

the day began with a plan, and we did a pretty good job of sticking to the plan. i cleaned our standing fans, we hung the curtains, and we headed to the mall to pick up all of mr smear's third-grade stationery, along with a new school bag and a watch with a SIM that we can use to get a rough idea of his whereabouts as well as enable us to communicate with him, without giving him a phone (which almost all the parents agree is a bad idea).

there's no way we could have handled the stationery shopping without the expert at the store. not a chance in hell.

i was relieved to have a meeting with the temple executive postponed regarding the mobile app i haven't touched in ages, and once i'd ingested sufficient caffeine i called horseman and we chatted for a long, long time. our main focus was blockchain stuff, but i was inspired to invest some time in an idea for a game i had this week.

which, in a roundabout way, led to mr smear and i playing two games of jones in the fast lane. that game is hard, and for all the right reasons. i love how mr smear really got into it, not only for his newfound appreciation for how much easier being a kid is, but also for him getting a grasp on some pretty adult concepts.

...

gd and i watched a bit more of the the need to grow documentary. we're about halfway through and as intriguing as some of it is, and as on point as some of the claims may be, there're things that have me raising an eyebrow and i had to look them up. the "power house" seems too good to be true, and it's really hard to take a documentary seriously when they present vandana shiva as a physicist, or any kind of authority.

...

my screen's started flickering randomly since i installed an updated driver earlier. that sucks.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.