Pitfalls of Global Settings Caching

-

 Caching and UX Design Challenges

I’m currently grappling with a frustrating issue where long-standing functionality suddenly collapses. Navigating the Ovid app is no small feat—it’s a massive, 20-year-old legacy system with a convoluted history and a labyrinth of operational "flows."

Recently, the system's reliability has been hit-or-miss. For example, upon logging into OvidUI, the system now defaults to Advanced Search instead of Basic Search. Even more baffling: clicking the "Basic Search" link does absolutely nothing. From a UX perspective, rendering a functional-looking link that provides zero feedback is inexcusable; even an error message would be preferable to total silence.

The Root Cause

My investigation revealed that "basic" was inadvertently stripped from modeTabOrder in ovidsp.ini during a consolidation of the .ini files and the subsequent Docker containerization. While this change was pushed back in February, it didn't surface until mid-May. This delay highlights a significant gap in our testing protocols.

The Pitfalls of Caching

While caching is a fundamental computer science tool for optimization, it can be a nightmare for debugging. In this instance, cached settings preserved the "correct" behavior for two months before finally expiring and revealing the bug.

I would argue that INI settings and defaults should never be cached. These files are small enough that the performance gains are negligible, yet they are critical to the software’s fundamental operation. We should focus on caching results, not configurations.

Comments

Post a Comment

Popular posts from this blog

Wolters Kluwer

-
  Wolters Kluwer So, I’ve started at Wolters Kluwer—weird name, I know. I was brought on as a Perl dev (backend, build/release, Linux admin), but suddenly I’m being tossed into the deep end of a super complex frontend. The real kicker? Everyone assumes I’m already a pro at this stuff. I never claimed to be, but the pressure is definitely on. Here’s the "short" list of things they expect me to just know , even though I’ve barely touched most of them: The Frontend Maze: JavaScript, jQuery, Ajax, SPAs, route handlers, and event listeners. The "Ovid" Ecosystem: It’s a massive app with a million ways to do the same thing. If you don't know the exact "UI path flow," you’re just chasing ghosts. The Tooling: Black Duck, Google Analytics, Open Telemetry, and Jenkins pipelines. The Meta Stuff: JIRA's crazy process flows (there are like 20 "similar" dropdown options for one task), Redis, and deep HTML/template structures that go way beyond basic...
Read more

Contingent worker - Code Games

-
A little chat with Gemini about Contingent workers and code games What is a "contingent worker'? A contingent worker is an individual who is hired by an organization on a non-permanent, as-needed basis. Unlike traditional employees, they do not have an implicit or explicit contract for long-term employment. Instead, their relationship with the company is "contingent" upon a specific project, a set period of time, or a particular business need. The term serves as an umbrella for several different types of work arrangements: Independent Contractors / Freelancers: Self-employed individuals who provide specialized services. They typically manage their own taxes and equipment. Consultants: Experts hired to provide professional advice or technical skills for specific organizational challenges. Temporary Agency Workers: Individuals employed by a staffing agency but "loaned" out to a client company for short-term assignments. Gig Workers: People who use digita...
Read more

The 5 AM Contract

-
Image
When "East Coast Time" Becomes "Anytime" When I signed onto this contract, I agreed to align with East Coast hours. In the world of standard business, that’s a clear 9-to-5 frame—or for me on the West Coast, a manageable 6 AM to 2 PM. It’s an early start, but it’s a fair trade for synchronization. Lately, however, those boundaries have begun to dissolve into a 24/7 "always-on" expectation that is as exhausting as it is unproductive. It started with "Code Games" initiatives creeping into my personal life—specifically, receiving texts on a Sunday morning to spend time looking into upcoming events.  Then came the after-hours messages once my 2 PM PDT cutoff had passed.  Now, the line has moved again: meetings are being scheduled for 5 AM. There is a massive difference between starting early to support a team and being expected to sacrifice sleep and weekends for non-urgent tasks. When we shift the "standard" day earlier and earlier, or rea...
Read more