Monthly Archives: July 2016

153: 2 Momentousness

Of music

Screenshot from 2016-07-09 23-50-53

Figure 1: a graph of my stats on after their great database crash in late June. However, the drop to 0 had nothing to do with that – that was the duration of my trip to Japan.

Screenshot from 2016-07-22 22-48-25

Figure 2: a graph of my stats now that I have begun work.

I took another step toward becoming an acceptable member of society on 2016-07-11. My scrobbles have stoically suffered accordingly. Gone are my lazy days of sitting at home, whiling the hours away with endless playlists. Gone is my freedom to saddle my ears and disappear into the music while working. These two graphs are to be remembered: their shapes together demarcate two huge portions of my life. My identity as a student reached its peak when the music disappeared; then the music came charging back in like a long-overdue tide (that is not how tides work but please ignore my rhetoric) for one last hurrah before it dropped off to pre-university levels abruptly. And so I shed my undergraduate skin to emerge as a bruised (yet pitifully, wholly unchallenged) functional adult.

Of reading

Before starting work, I flung myself to the halfway-mark of The Two Towers (a little ways into book 4). When conscription peeked over the horizon (about a week’s clearance, I think), I put it on hold and picked up the borrowed copy of Leningrad: Siege and Symphony and got about 200 pages (out of 500) in. The rest I finished during bus rides to and from work. I plan on finishing The Lord of the Rings, then moving onto Steve Jobs. From there I still have 1Q84 and Code Warriors.

Of watching

I went to see Finding Dory last weekend; it was good! I look forward to Star Trek Beyond in a few weeks; by then, hopefully Fantastic Beasts and Doctor Strange will ramp up advertising. I will polish off the year with Rogue One – realistically, seeing it in late January.

Of working

I’m 2 weeks in. I feel good about things. The usual anxiety is still there, but nice people do wonders for the nerves. I can rise every morning and look forward to getting into the office – so that’s winning, isn’t it?


152: Chase Bank


I returned from abroad a week and three days ago. It was around that time that I noticed Chase Online Banking stopped working for me, though it worked just fine on the burner computer I carried with me while away from home. I wasn’t terribly worried until a few days ago when I realized that this supposed outage (for that was what the webpage informed me it was) had been going on entirely too long without any ripples on either Google News or Twitter. Was this a problem specific to me?

I called up customer support and predictably achieved no real results. They fed me a presumable red herring by waffling about some known issue that their technicians were fixing. But at least Suzanne was honest to tell me directly that there was no systemwide outage that they knew of, and so the problem was probably on my end. (Hubris erroneously told me otherwise.) It only occurred to me today to change up my approach to see if I could isolate the problem.

First I went back to my burner computer (SL7 with Google Chrome on permanent incognito mode). I was thunderstruck when I logged in without issue. Second, I repeated this feat on my normal workstation with Firefox Nightly. This ruled out Chase implicitly blacklisting Linux or Firefox setups. I hung my head in shame. The fault was mine, then.

I cleared my cache, cleared out my Chase cookies, and restarted Firefox. No good.

Some devil or angel whispered in my ear and I glanced at NoScript while the redirection transitioned me from a spinner-on-blank-page to the boilerplate outage page. I managed to catch sight of NoScript blocking out one I added the same to my whitelist. Login, success! facedesk.

Let this story remind me from time to time that just because I know how to clear my cache and cookies (and also know what both of those are) doesn’t mean I get to assume nothing is ever my fault.