You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Many of Yimon's support tickets related to her desktop and laptop lead to successfully addressing symptoms, and not addressing underlying structural issues implied to exist. Thus, now deemed worth having one place to capture those tickets, at least on-going, for future reference. This situation is expected to only get worse if this pattern continues, alas.Tickets and events to be listed in reverse-chronological order (most recent ones first):

TicketDate openedRelated info
INC0000022175314/12/2018Oliver states that as of 5/7/2018: Yimon again did not follow up with us as she stated were her intentions.

It's getting increasingly risky to update anything on her systems as she only wishes to (1) engage when there is a problem (and that is almost always in deadline-crisis mode), and (2) only willing to invest to fix symptoms and not in getting the system into a known, good state, even at a later time.

The Issue now is that getting to (2) now, with the mounting delayed maintenance and versioning issues, would require a re-install in my opinion. AND it would still be risky because of versioning issues (driven by saving money on licensing?). Uncertainty layered on uncertainty: Hard drive space limits, active use of syncing tools (including non-Cornell Dropbox), inter-related software not all of which is current (does the use of older versions of some software represent a consequence of a licensing-cost avoidance strategy?).

  

Is it worth going back and pulling out the history of tickets in which Yimon reports a problem following this patter, or just collect them from this point forward?

These problem reports are usually characterized by a crisis-before-a-deadline, followed often by our heroic, quick solutions. With the increased caveat that she got lucky that time, but don't expect such luck next time. Usually each crisis also involves a discussion about what is actually needed to prevent a future problem, but no follow-through permitted by Yimon. The 4/12/2018 ticket created above is representative of this pattern we're observing.

  • No labels