Voting is open for the next 1 day, 3 hours
*forlornly stares at three stacks of publications in the To Read pile and an unfinished lesson plan for tomorrow*

Aye, my sentiments as well.

*enormous sympathy*

*stares at open MfD tabs that I am super excited to deal with*
*stares at stacks of books I want to read for self improvement*
*stares at folder on my laptop full of cool MOOC videos*
*stares at list of online resources I want dig into through*
*...*
*stares at folder full of technical papers for project 1*
*stares at folder full of technical papers for project 2*
*stares at folder full of technical papers for project 3*

*...cries*

*looks at broken lab equipment number 1*
*looks at broken lab equipment number 2*
*hides from younger grad students who need me to fix it*
*looks at data that needs to be processed*
*looks at job applications*
*hides from supervisor*

My sincerest sympathies to you both.
 
Omake: Observe, Contain, Repair
Omake:
Observe, Contain, Repair

Subject#: OCR-48617
Threat Class: Indra
Security Level: 4

Observation & Containment Requirements:
Following Incident#-■■■■■■■■-■ and shortly thereafter, Incident#-HENGE-05, OCR-48617 has been upgraded to threat class "Indra." In addition to observing all I5 protocols, OCR-48617 is to be monitored at all times by an SDU which includes, at minimum, one senior antimemetics researcher. The SDU on duty must be rotated at random intervals, spanning no less than three hours and no greater than twelve hours. In the event a Shift is detected, the SDU must immediatately notify HQ and report for reassignment.

All standard Exposure-related OCR protocols remain in effect.

Description:
OCR-48617 was initially brought to our attention after apprenticing under rogue agent ■■■■■■■■■■ (OCR-7975). OCR-7975's efforts have continued to confound all but the most cursory of observation attempts until it was arranged to separate the two under pretense of OCR-48617's chuunin candidacy examinations (see below).

Following Incident#-7589751 (see report {REDACTED} by CA-5332), OCR-48617 experienced unmitigated full Exposure for roughly fourteen seconds as a result of an infusion failure. CA-5332 performed an on-site examination for Exposure Contamination and concluded negative for Class C or greater effects, but was interrupted by OCR-7975 before examination was completed. At the request of {REDACTED}, CA-5332 agreed to detain OCR-48617 for further examination and managed to arrange such to avoid triggering OCR-7975's suspicions. An attempt was made to fit OCR-48617 with a standard LU-9C45Z remote observation transponder, but the device was discovered and removed by OCR-7975 before activation, later threatening:

"IF YOU STINKING STINKERS EVEN SO MUCH AS THINK TO LUPCHANTZ MY APPRENTICE I WILL MAKE {REDACTED} LOOK LIKE {REDACTED}"​

Following CA-5332's recommendations, OCR-7975 has been allowed to personally observe OCR-48617 for signs of Progression, conditional on timely delivery of weekly reports.

Note: Following Incident#-■■-■■■■-■, protocol has been to avoid any and all direct contact with OCR-7975. OCR-7975, for all his paranoid delusions, remains among the most capable counter-■■■■■■■■■■■■ agents the organization has ever known... and is otherwise mostly harmless.

Reports indicate that OCR-48617 was primarily responsible for Incident#-7852373, resulting in a Class-B Dimensional Breach. However, the dispatched BCU reported that Rift Protocol Three had already been satisfactorily enacted, allowing for swift and effortless containment and repair.

As part of an ongoing initiative to determine the cause of numerous unexplained Shifts relating to events, individuals, and locations around OCR-48617, OCR-48617 was fitted with a LU-9C45Z remote observation transponder during an opportune moment during the fourth event of the aforementioned chuunin candidacy examinations. Almost immediately thereafter, Incident#-■■■■■■■■-■ was recorded and archived. Further, the residual counter-possible dimensional signature matched that of Incident#-HENGE-05.

Additionally, the details of the circumstances surrounding the incident is consistent with several of the aforementioned unexplained Shifts. To wit: there appears to be a statistically anomolous preferential enumeration of Yadoian Inconsistencies in Murokawa Branches wherein OCR-48617 faces exceptional adversity.

As a result, OCR-48617 has been upgraded to threat class "Indra" with all due implications.
 
Last edited:
How old is Jiraiya? Maybe he was trained by those from Whirlpool?

We should ask him who trained him some time.

According to the timeline I put together for my unwritten fanfic, using the founding of Leaf as the epoch, Jiraiya died at 54 in canon, in year 66, meaning he was born in year 12.

This quest is currently in year 64, so Jiraiya should be 52.
 
Last edited:
I'm just here to take my mind off the fact that a series of alerts signifying a cascading backend service failure could arrive any second. It's probably better than alcohol as a coping mechanism.
 
Hey guys, I was hacking @eaglejarl's computer again for... uh... reasons, and anyway I found something really interesting from a folder he probably thought was encrypted enough to hide:
Yep, because having established that our technologically-gifted and morally ambiguous player base finds getting the QM docs' passwords easier than taking candy from a baby, we'd never plant misleading information where we knew someone would find it.

Oh, I'm sorry. WWDTTY?

I'm just here to take my mind off the fact that a series of alerts signifying a cascading backend service failure could arrive any second. It's probably better than alcohol as a coping mechanism.
Marked for Death: it takes away the pain ameliorates the pain replaces the pain with an equal but different kind of pain you know what, I'm not even sure why you people keep coming back.
 
Last edited:
*enormous sympathy*

*stares at open MfD tabs that I am super excited to deal with*
*stares at stacks of books I want to read for self improvement*
*stares at folder on my laptop full of cool MOOC videos*
*stares at list of online resources I want dig into through*
*...*
*stares at folder full of technical papers for project 1*
*stares at folder full of technical papers for project 2*
*stares at folder full of technical papers for project 3*

*...cries*

*stares at programming milestones he is super excited to work on*
*stares at list of paper talk videos he wants to watch*
*stares at list of background papers he's been ignoring for 8 months*
*stares at CI he has to setup*
*stares at pile of obtuse bugs he has to fix*
...
*goes back to reading fanfic*


I don't know what you're complaining about.



More seriously:
  • Skim papers first, only read them if they're interesting/useful enough after the skim. Ping me if you want to know how to skim effectively.
  • If you can find slides or talks for papers, watch those instead.
  • Videos should be played faster than 1x if you can handle it.
  • Automate things you can automate.
 
@firestorm440 that image doesn't like hotlinking. Maybe download and re-up to imgur?

Edit:

I pulled some wizardry, on mobile.

Here's the image.

 
Last edited:
As someone whose job can be summed up as robustly automating predictable and well-defined processes, my advice is not to do this.

As someone whose job is to robustly automate chaotic and ill-defined processes that currently can only be performed by humans, (i.e. electrical engineering) I wish I had your job.

Well not really, but I do think as a grad student, setting up a bit of automation around your workflow is rather important. Make it so that starting common tasks is a one click operation, (e.g. Have a big Google drive folder of papers to read, a script that picks one out for you, and opens a text editor for notes, and when you're done moves both the paper and notes to an already done folder. Or a way to automatically find a bibtex entry for a paper via Google scholar.)

It saves so much time overall.
 
Voting is open for the next 1 day, 3 hours
Back
Top