Wolters Kluwer

When Corporate Bots Strike Back For a while now, I’ve been dodging a bot named LEO. Its sole mission in life? To pester me with a one-question "survey" to select my "language preference." I ignored it as long as I could because, frankly, the irony was too much to handle. LEO was asking me— in English —what language I prefer. Logic dictates that if I didn’t understand the prompt, I wouldn't be able to answer it, and if I could answer it, the question was already moot. It’s the digital equivalent of someone walking up to you and asking, "Excuse me, do you speak to people?" Eventually, I learned that this wasn't just a quirky bot; it was yet another piece of mandatory corporate administrative overhead. So, I finally gave in. I clicked "English." I confirmed what was already painfully obvious. My reward for finally complying? A mandatory class. Apparently, identifying my language preference wasn't the finish line; it was the enrollment t...

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...

When Perl vanishes I don't really think I'm going nuts here, but this is very confusing. Ajay asked me to pick up stuff from the backlog that is Perl-related that I think I can handle. So I look into the backlog, and the ticket titles have [Perl] in them to indicate Perl, right? The first one I look at is about creating a config of some sort. I notice it's Code Complete! Oh Ok. Interested in what the Perl code changes are I looked at the PR, and not a single file or change had any Perl in it. JSON files, some kind of ERB file, and a changelog.md file... ¯\_(ツ)_/¯

  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...