#Typing Automation Software

[instantdataservices]

Hii Everyone! I Hope all are doing well

Medical Insurance Auto-Fill Software is a specialized tool designed to streamline and automate the process of filling out medical insurance claim forms and related documentation. The software is developed to enhance efficiency, reduce errors, and save time.

Implementing Medical Insurance Auto-Fill Software can contribute to a more streamlined and accurate claims submission process, reducing the administrative burden on data entry works

Thank you for watching, hope our video may helps you, for more helpful videos and relatable video please subscribe our channel, do share , follow and like the video.

[roseband]

he literally just said on a rally (why is he even doing them still wtf) that he wants to bring the economy back to 1929 we're all so fucking screwed.... we're so fucking screwed

the social stuff can be mitigated... this can't, we're so screwed globally :|

[rvsdataconversion]

MI demography form filling auto typing software

Utilizing MI demography form filling auto typing software is the key to automate medical insurance form filling, offering a powerful software for MI data entry auto typing that answers the question of how to fill MI demography form automatically and functions as a dedicated form filling auto typer and Medical insurance auto filler, ultimately serving as an efficient MI data entry automation tool…

[1auditmanagementsoftware]

Audit Management System Software

The "Audit Management System Software" in 1Audit is designed to support and simplify the audit process. It allows for seamless management and monitoring of audit files anytime and anywhere. With features like document control, collaboration, professional compliance, and cloud-based access, it ensures efficient task management and secure document storage. The software helps streamline audit workflows by automating essential processes, managing user permissions, and supporting communication among audit teams, ultimately improving the audit's accuracy and effectiveness.

[yethiconsulting]

How to Create Effective Test Cases for Functional Testing

Creating well-structured test cases is essential for ensuring the accuracy and reliability of functional testing. A well-written test case helps testers validate software functionality, detect defects, and improve overall quality.

Steps to Create Effective Test Cases

Understand Requirements – Analyze functional specifications, user stories, and business rules to ensure comprehensive coverage.

Define Clear Objectives – Each test case should focus on a specific function or feature with a clear expected outcome.

Write Detailed Test Steps – Provide step-by-step instructions for execution, including input values, actions, and expected results.

Ensure Test Case Independence – Design test cases that can be executed independently to avoid dependencies and inconsistencies.

Include Positive & Negative Scenarios – Cover both expected behavior (positive testing) and edge cases (negative testing) to improve software testing robustness.

Prioritize Test Cases – Identify critical test cases that address high-risk functionalities and execute them first.

Leverage Automation Where Possible – Automate repetitive test cases to enhance efficiency and accuracy.

Conclusion

Effective test cases enhance functional testing by improving defect detection, reducing rework, and ensuring software reliability. Following best practices and continuously refining test cases helps achieve higher software quality and better user experience.

[aarunresearcher]

United States marketing automation market size reached USD 19.1 Billion in 2024. Looking forward, IMARC Group expects the market to reach USD 53.8 Billion by 2033, exhibiting a growth rate (CAGR) of 12.2% during 2025-2033. The rising focus of marketers on strategic initiatives, creative campaigns, and more robust customer relationship management is primarily driving the market growth across the country.

[charlessmithpost]

What are the types of XPath?

XPath is a query language used for navigating and querying XML documents. XPath provides a way to navigate through elements and attributes in an XML document.

There are two main types of XPath expressions: absolute and relative.

Absolute XPath:

Absolute XPath starts from the root of the document and includes the complete path to the element.

It begins with a single forward slash ("/") representing the root node and includes all the elements along the path to the target element.

For example: /html/body/div[1]/p[2]/a

Relative XPath:

Relative XPath is more flexible and doesn't start from the root. Instead, it starts from any node in the document.

It uses a double forward slash ("//") to select nodes at any level in the document.

For example: //div[@class='example']//a[contains(@href, 'example')]

XPath can also be categorized based on the types of expressions used:

Node Selection:

XPath can be used to select nodes based on their type, such as element nodes, attribute nodes, text nodes, etc.

Example: /bookstore/book selects all <book> elements that are children of the <bookstore> element.

Path Expression:

Path expressions in XPath describe a path to navigate through elements and attributes in an XML document.

Example: /bookstore/book/title selects all <title> elements that are children of the <book> elements that are children of the <bookstore> element.

Predicate:

Predicates are used to filter nodes based on certain conditions.

Example: /bookstore/book[price>35] selects all <book> elements that have a <price> element with a value greater than 35.

Function:

XPath provides a variety of functions for string manipulation, mathematical operations, and more.

Example: //div[contains(@class, 'example')] selects all <div> elements with a class attribute containing the word 'example'.

These types and expressions can be combined and customized to create powerful XPath queries for different XML structures. XPath is commonly used in web scraping, XML document processing, and in conjunction with tools like Selenium for web automation.

[ourjobagency]

Most youngsters prefer the software tester role to make a reliable career without hard efforts. This role is responsible for the quality of software deployment and development.

[sexhaver]

definitely one of the most difficult moments of my professional career was when i was doing tech support for [REDACTED]'s automated biomed research lab and like. hang on lemme greentext this

>tell them i can fix this issue in half an hour with a remote support session (aka Teamviewer)

>"you want to... control our computers???? over the internet????? like some kind of HACKER???????"

>their IT submits my request to upper management and after two weeks they reluctantly allow me to get remote access to their systems

>by logging into a virtual machine using a 20-digit password and then using a specific program inside of that virtual machine

>while sharing my screen with someone from their IT team the entire time

>finally get remote access to the PC with the issue

>go to open log files to start troubleshooting

>ERROR: User does not have read permissions.

>what the fuck

>ask their IT guy why it's saying that

>"...because we don't want you looking at our stuff, duh?"

>take deep breath before calmly explaining that i need to open files in order to fix their problem

>IT guy submits my request to upper management

>after another week i go through the whole process again but can actually open the log file this time

>cool, it's exactly the issue i thought it was and i know exactly how to solve it

>open the relevant settings file, change a single number, hit Save

>ERROR: User does not have write permissions.

>what the FUCK

>ask IT guy how i'm supposed to fix their system if i can't change literally anything on it

>takes 20 minutes of arguing to get him to admit that maybe i need write access

>he submits the request to upper management

>a week goes by

>upper management denies it

>says i can just verbally tell the IT guy on the call what to type and he'll do it for me

>deep breaths. deep breaths.

>start third remote session

>go to open the relevant .log file in notepad, which isn't the default program it opens with for some reason

>they fucking disabled right clicking

>[REDACTED] has a $118 billion market cap btw

>manage to walk the IT guy through using the command line (which he had never seen before and was scared of) to edit the relevant file

>three weeks go by

>new support ticket in my inbox

>"why didn't your fix fix this completely unrelated issue?"

>they still won't give me write access

>VP of [REDACTED] yells at me in our weekly meeting for taking so long to fix a third unrelated issue they never submitted a ticket for and is also not actually an "issue" but an intended feature of our software that they don't like

>i went to college for this

[nostalgebraist]

So, about this new "AI 2027" report...

I have not read the whole thing in detail, but my immediate reaction is kind of like what I said about "Bio Anchors" a while back.

Like Bio Anchors – and like a lot of OpenPhil reports for that matter – the AI 2027 report is mainly a very complex estimation exercise.

It takes a certain way of modeling things as a given, and then does a huge amount of legwork to fill in the many numeric constants in an elaborate model of that kind, with questions like "is this actually a reasonable model?" and "what are the load-bearing assumptions here?" covered as a sort of afterthought.

For instance, the report predicts a type of automated R&D feedback loop often referred to a "software intelligence explosion" or a "software-only singularity." There has been a lot of debate over the plausibility of this idea – see Eth and Davidson here for the "plausible" case, and Erdil and Barnett here for the "implausible" case, which in turn got a response from Davidson here. That's just a sampling of very recent entries in this debate, there's plenty more where that came from.

Notably, I don't think "AI 2027" is attempting to participate in this debate. It contains a brief "Addressing Common Objections" section at the end of the relevant appendix, but it's very clear (among other things, simply from the relative quantity of text spent on one thing versus another) that the "AI 2027" authors are not really trying to change the minds of "software intelligence explosion" skeptics. That's not the point of their work – the point is making all these detailed estimates about what such a thing would involve, if indeed it happens.

And the same holds for the rest of their (many) modeling assumptions. They're not trying to convince you about the model, they're just estimating its parameters.

But, as with Bio Anchors, the load-bearing modeling assumptions get you most of the way to the conclusion. So, despite the name, "AI 2027" isn't really trying to convince you that super-powerful AI is coming within the decade.

If you don't already expect that, you're not going to get much value out of these fiddly estimation details, because (under your view) there are still-unresolved questions – like "is a software intelligence explosion plausible?" – whose answers have dramatically more leverage over your expectations than facts like "one of the parameters in one of the sub-sub-compartments of their model is lognormally distributed with 80% CI 0.3 to 7.5."

---

Maybe this is obvious, I dunno? I've just seen some reactions where people express confusion because the whole picture seems unconvincing and under-motivated to them, and I guess I'm trying to explain what I think is going on.

And I'm also worried – as always with this stuff – that there are some people who will look at all those pages and pages of fancy numbers, and think "wow! this sounds crazy but I can't argue with Serious Expert Research™," and end up getting convinced even though the document isn't really trying to convince them in the first place.

---

Now, if you do buy all the assumptions of the model, then yes, I guess this seems like a valuable exercise. If you are literally Daniel Kokotajlo, and hence believe in all the kind of stuff that Daniel Kokotajlo believes, then it makes sense to do all this legwork to "draw in the fine details" of that high-level view. And yeah, if you think the End Times are probably coming in a few years (but you might be able to do something about that at the margins), then you probably do want to get very precise about exactly how much time you have left, and when it will become too late for this or that avenue for change.

(Note that while I don't agree with him about this stuff, I do respect Kokotajlo a lot! I mean, you gotta hand it to him... not only did he predict what we now call the "Gen AI boom" with eerie accuracy way back in 2021, he was also a whistleblower who refused to sign OpenAI's absurd you-can't-talk-about-the-fact-that-you-can't-talk-about-it non-disparagement agreement, thereby bringing it into public view at last.)

But, in short, this report doesn't really touch on the reasons I disagree with short timelines. It doesn't really engage with my main objections, nor is it trying to do so. If you don't already expect "AI" in "2027" then "AI 2027" is not going to change your view.

[anachronisims]

How to EFFECTIVELY Use Empty Standby List to Reduce Flashing and Crashing

This tutorial is for TS2. Obviously. This is virtually the last "chapter" of advice for the Pink Flashing Survey Report (still forthcoming as a single readable thing but posted in bits and pieces over the last six months). PS it's a lonnnnnnng post. Ctrl+F "tldr" for the very short version once you open the cut.

"Part 1" of the Empty Standby List ("ESL") tutorial was already written comprehensively with screenshots by Digi at her wordpress. Following Digi's tutorial will get you set up with ESL as a routine automated background task your computer runs, typically every five minutes.

@gayars set up two instances of the routine, each running every five minutes, staggered two/three minutes apart. In other words, task 1 runs at 12:00, task 2 runs at 12:03, task 1 runs at 12:05, task 2 runs at 12:08, etc. However, I found that this negatively impacted the graphical performance of my game, notably by having the ESL task window flash over the game window, which I had never seen before, nor since reverting back to a single 5-minute task routine.

Anyway. Go do Digi's tutorial if you haven't already; I'll wait.

Background on Why this Matters

So, now your computer will be wiping the standby memory every five minutes. The thing is, this won't be able to have much impact on your game unless you wait to let it wipe before you do a major loading action.

Major loading actions are, in general order of strain (most to least strenuous):

Loading a full neighborhood.

Loading a large (3x4 or bigger) populated lot.

Loading a large unpopulated lot.

Loading actual CAS, if you have a lot of non-defaulted CC.

Loading a medium (3x3) populated lot.

Loading a medium unpopulated lot.

Loading a small (2x3 or smaller) populated lot.

Loading a small unpopulated lot.

Loading CAS catalogs from within a lot (e.g. using FFS clothing tool, "Change Appearance" on the mirror, shopping for clothes/trying on clothes on a community lot).

Turning up your lot view settings (generating other lots' lot imposters within your current lot)/panning the camera around.

You should already be doing at least all medium- and large-lot loading with the Lot View Settings Juggling Method, and “uint LotSkirtIncrease” removed from your userstartup.cheat - otherwise whenever you load a lot you are compounding the strain by also having the neighborhood load at the same time.

Using Resource Monitor Effectively

If you watched the Jessa Channel tutorial on flashing, she recommended downloading a third-party RAM usage monitoring software. This is unnecessary. For purposes of reducing your crashing, all you need is the native Windows program "Resource Monitor" that she also recommends.

To open it:

Click the Windows symbol/start menu.

Begin typing "Resource Monitor."

Click Resource Monitor when it shows up.

Once it is open, get to the useful information:

Click the "Memory" tab.

Make sure the "Processes" and "Physical Memory" subs are fully open, as above.

Sort by "Commit (KB)."

Each time you reopen Resource Monitor, it should restore your last view settings, so you won't have to repeat these steps.

While Resource Monitor is still open, "Pin" it to the taskbar so it will always be readily accessible.

Right-click the icon on the taskbar.

Click "Pin to taskbar."

If it says "Unpin from taskbar" you have already done this step :)

Now comes the monitoring part. You will focus on the dark-blue "Standby" block of the bar graph on Physical Memory.

Every fifth minute, when the ESL task runs, this will flash down to 0 and then pop up to about 30-75, depending on what you are doing. It will go higher faster if you are doing stuff, obviously, and hover pretty low if your computer is just sitting still. TLDR the remainder of this tutorial: only take stress actions when Standby is below 100.

As we all know too well, TS2 has a 4gb RAM limit. The problem is, TS2 seems to count the memory that is in standby, too, not just the committed/working set. Thus, before you take a major loading action (that is going to push up to 1.5gb into Standby), you need to wait for Standby to wipe so the game doesn't accidentally think it's using more memory than it is. Got it?

This is how much RAM my game is using when my neighborhood opens, pretty closely zoomed in on any particular lot. If it is zoomed out further - like a whole city block - both committed and working set are easily over 2.2gb. When I pan around the neighborhood, it continues going up. Portions of the hood that go back out of view seem to get relegated to standby, but yes, my game has crashed just from looking too much at my neighborhood from too wide an angle. Unless I slow down and let ESL run before moving on to the next section.

Six months of diligent Resource Manager monitoring has resulted in substantial reductions of crashing and flashing on my first hood view load and first lot view load. It is not 100% guaranteed, but it cuts it back to Very Playable Levels. And when I have tested the theory by purposefully not letting ESL run before a stress point, it always flashes and/or crashes within the next couple minutes.

SO! Here's what I do when I'm launching my game.

Because of overheating concerns, I always fully shut down my computer when I'm not using it for more than an hour. If I have been playing and experience a flash or crash, I will restart before trying again. @infinitesimblr, a survey Respondent who reported virtually no flashing or crashing despite a vast CC catalog, also recommends restarting between using Bodyshop or SimPE and the full game. I have found it may make a difference with Bodyshop (which I use too rarely to make a pseudoscientific claim) but that I have found basically no impact going from SimPE to the game. YMMV.

Immediately after Windows is done loading, I open Resource Monitor and wait a few minutes. Often background updates begin running and the Standby bar goes crazy - sometimes filling up the entire available RAM - and I just let it sit and do its thing. (Usually I start the computer right before my kid's bedtime so I am not actively waiting on it or anything. Go take a shower or make a sandwich or drink some water, like you did in the old days when the game itself took 20 minutes to load.)

Once the standby bar levels out and is consistently peaking no higher than about 250mb between ESL wipes, after the next ESL wipe, I will launch the game. (Usually between logging into Windowsat the beginning of storytime and checking Resource Monitor before we go do tuck-in, it is reliably hanging out below 100 unless a big TS4 or Windows update was downloading.)

Reminder: do not delete thumbnails anymore prior to launching the game. I also have turned off RPC's clear caches option and have observed faster loading times with minimal increases in crashing.

After the neighborhood selection screen comes up, wait for ESL to run again before opening your neighborhood.

If you have continue to have more than VERY sporadic hood load flashing after taking these steps, you should try launching into a subhood if you have one, then pivoting to the main hood if that's where you're playing that session after yet another ESL wipe. If that doesn't help you simply need to thin out your hood or accept the flashing. (I ended up deleting about 25% of my deco trees and 10-15 outer-lying lots that will be re-placed in a subhood.)

After the hood is loaded, navigate to the lot you want, but DO NOT actually load that lot until ESL runs yet again. Ditto for CAS - Do not select "Create New Family" until ESL has run again.

Play should be proceed as normal at this point. You probably don't need to alt-tab back to Resource Monitor again unless your sims are going traveling or you are changing play lots.

BONUS TIP #1: You can put a shortcut to the ESL routine on your desktop and push it manually (just double click the icon) if you don't feel like waiting once the game is loaded. I have had imperfect results with this vs. just waiting the five minutes, though, because the game wants to run through some stuff and flush it. But it's an option for you to experiment with.

BONUS TIP #2: If you have a really deep clothing/hair CC catalog, try to avoid using the FFS clothing tool option where you select every outfit for the sim, and their hair and makeup, at the same time. Instead, choose individual outfits by type and use the regular mirror option to change appearance (or SimBlender has it, I think, so they can do it where they already are).

[probablyasocialecologist]

The Brutalist’s most intriguing and controversial technical feature points forward rather than back: in January, the film’s editor Dávid Jancsó revealed that he and Corbet used tools from AI speech software company Respeecher to make the Hungarian-language dialogue spoken by Adrien Brody (who plays the protagonist, Hungarian émigré architect László Tóth) and Felicity Jones (who plays Tóth’s wife Erzsébet) sound more Hungarian. In response to the ensuing backlash, Corbet clarified that the actors worked “for months” with a dialect coach to perfect their accents; AI was used “in Hungarian language dialogue editing only, specifically to refine certain vowels and letters for accuracy.” In this way, Corbet seemed to suggest, the production’s two central performances were protected against the howls of outrage that would have erupted from the world’s 14 million native Hungarian speakers had The Brutalist made it to screens with Brody and Jones playing linguistically unconvincing Magyars. Far from offending the idea of originality and authorship in performance, AI in fact saved Brody and Jones from committing crimes against the Uralic language family; I shudder even to imagine how comically inept their performances might have been without this technological assist, a catastrophe of fumbled agglutinations, misplaced geminates, and amateur-hour syllable stresses that would have no doubt robbed The Brutalist of much of its awards season élan. This all seems a little silly, not to say hypocritical. Defenders of this slimy deception claim the use of AI in film is no different than CGI or automated dialogue replacement, tools commonly deployed in the editing suite for picture and audio enhancement. But CGI and ADR don’t tamper with the substance of a performance, which is what’s at issue here. Few of us will have any appreciation for the corrected accents in The Brutalist: as is the case, I imagine, for most of the people who’ve seen the film, I don’t speak Hungarian. But I do speak bullshit, and that’s what this feels like. This is not to argue that synthetic co-pilots and assistants of the type that have proliferated in recent years hold no utility at all. Beyond the creative sector, AI’s potential and applications are limitless, and the technology seems poised to unleash a bold new era of growth and optimization. AI will enable smoother reductions in headcount by giving managers more granular data on the output and sentiment of unproductive workers; it will allow loan sharks and crypto scammers to get better at customer service; it will offer health insurance companies the flexibility to more meaningfully tie premiums to diet, lifestyle, and sociability, creating billions in savings; it will help surveillance and private security solution providers improve their expertise in facial recognition and gait analysis; it will power a revolution in effective “pre-targeting” for the Big Pharma, buy-now-pay-later, and drone industries. Within just a few years advances like these will unlock massive productivity gains that we’ll all be able to enjoy in hell, since the energy-hungry data centers on which generative AI relies will have fried the planet and humanity will be extinct.

3 March 2025

[rvsdataconversion]

Cibil Management form filling auto typing software

The CIBIL Management Form Filling Auto Typing Software, also known as the MI Demography Form Filling Auto Typing Software, is a powerful tool that includes the MI Demography Auto Typer and CIBIL Management Auto Typer modules—making it the perfect solution for fast, accurate data entry using an advanced Data Entry Auto Typer system Cibil Management form filling auto typing software Demo…

[1auditmanagementsoftware]

Audit Planning Software

1Audit's Audit Planning Software helps streamline the audit planning process by providing tools for document control, team collaboration, and compliance management. It allows users to organize and manage audit documents securely, ensures efficient communication among audit teams, and supports adherence to professional standards. The software is cloud-based, enabling secure access to audit files from anywhere, making the planning process more efficient and organized.

[malk1ns]

march 15 v devils, 7-3 win

nice.

i really enjoyed geno's bizarro over-the-top penalty fugue state he went into for this one. almost like he was glitching out...

we can call this a homage to @sevenfists' wonderful tragic hockeybot geno, but not as good because like...duh.

this does contain a homophobic slur just fyi.

Evgeni has followed a fairly strict game-day protocol ever since he woke up in Pittsburgh almost 20 years ago. The details have changed, refinements and efficiencies added in as his software was upgraded, but the basics, the stuff that keeps him running at optimal performance and giving his all on the ice, have remained the same.

Most of his start-up process is automated now, thankfully. Those first couple of years he needed to be manually disconnected from his charging station and powered on every morning, and since the station was bulky and he had to charge upright all night he’d spend the first half-hour trying to loosen up his joints and walk without a hitch in his step. It also meant he had to stay at the rink—the unit was permanently installed in his maintenance room, and they only had one more extraordinarily bulky one that got lugged around for road trips. Evgeni spent a lot of mornings after Dana woke him up wandering the hallways until the rest of the guys started to trickle in.

He came back from the Olympics in Sochi with a new charging port, discreetly installed under his left armpit and USB-C compatible provided it’s connected to one of his new, portable power packs. The automated start-up patch came through shortly after, and all he had to do was program in a power-down and power-up time and he boots up all on his own.

Powering down in a comfortable position had been a revelation. Being able to do it wherever he wanted was another.

Evgeni considered buying his own house—the idea of his own space is appealing, even if he’s not quite sure what people do at home by themselves at night. He’d run a pro/con analysis, though, and asked someone to look over the results to verify the conclusion he came to: however unlikely it may be, the scenario of something going wrong when nobody is there to find Evgeni and perform emergency maintenance is an unacceptable trade-off for home ownership.

Sidney’s suggestion that Evgeni just move in with him was much more logical.

Something else that came with Evgeni’s 2014 upgrade was an unexpected, but not unwelcome, libido add-on. All part of the goal to make Evgeni and others like him more human, integrate them more into society at large. It took a few months for Evgeni to calibrate to his new desires; he’d expected a standard program, especially with his lab of origin located in Russia, but after a while he figured out he was gay.

He spent the off-season experimenting and arrived in Pittsburgh for the season with a list of likes and dislikes, and a type. Sidney almost exactly matched the latter, and based on Evgeni’s new experience he was confident that the first two items could be adjusted to suit.

He’d been right. 

Sidney has said he’s in love with Evgeni. Evgeni’s emotional response center has been upgraded on a regular basis over the years, but most of the time it seems like he’s a little…slow, maybe, or removed from how he should be feeling, such as it is.

Not about Sidney. He’s pretty sure he loves Sidney too.

Sidney also understands the value of a routine. He has his own, more rigidly engrained than anything Evgeni does on gameday, and he’s more than happy to leave Evgeni alone to boot up and run his diagnostics in peace. It’s unsettling to watch, Evgeni’s been told—his eyes go disconcertingly blank, and for a solid five minutes he’s utterly unresponsive. People get weird about it, even if they’ve seen it before. He prefers to be alone.

Mid-March in a season like this one is a grind. Evgeni’s been in for repairs more this season than the last two combined, and they might not be officially eliminated from playoff contention yet but it’s just a matter of time; motivation is hard to come by, even for Evgeni. It’s reassuring to fall into his programming and run through each system one by one, making sure he’s primed for optimal performance.

There’s a spark in the corner of his vision.

Evgeni pauses, scrolls back through lines of code, reviews. Nothing. He must have imagined it.

When he pulls himself out, he’s running a few minutes late; Sidney will be almost done with his breakfast.

Evgeni heaves himself to his feet and heads downstairs. Sidney drives on game days, so Evgeni downloads the Devils’ five most recent games to review in the car.

—

He shouldn’t need to, but Evgeni likes to top-up his charge while Sidney takes his pre-game nap. Sidney likes it too, says it feels like they’re falling asleep together; it also helps that once Evgeni’s powered down he doesn’t move, so once they’re arranged to maximize Sidney’s comfort there’s no mid-sleep jostling.

When Evgeni boots back up, he feels…weird. Wrong, lying in bed with Sidney wrapped around him like normal.

He unplugs his charger and extracts himself as carefully as he can, putting on his suit and making his way downstairs to wait until Sidney is awake and ready to drive them to the rink for the game.

Sidney frowns at him when he finally comes down, but Evgeni turns his head, and Sidney lets him be.

They make small talk in the car like usual, but Evgeni’s distracted, and eventually Sidney goes quiet. To distract himself Evgeni runs back to his source code, a well-worn self-soothing mechanism when he’s feeling jumpy or off.

The code itself is simple but effective, wrapped inside a descriptor of the reason Evgeni was made in the first place.

The modern sport of ice hockey was developed in Canada…

By the time the game starts Evgeni’s restless, shifting from foot to foot during the anthem and eyeing the opposing team with more hostility than he’s used to experiencing. 

Evgeni’s never pretended to be the cleanest player in the league. He’s sneaky with his stick, takes risky penalties because when guys hit back he doesn’t feel pain like humans do, and sometimes it works. Even for him, though, this game is tough sledding.

When his reckless double minor results in a goal against and lets the Devils draw within one, Evgeni shatters his stick in the box, then glides back to the bench with his mouth twisted in a frown. He feels—he wants to hit something, or maybe someone.

His higher processing is on alert at this aberration in behavior, but all Evgeni can do is sit on the bench, accept his new stick, and wait.

“G,” comes Sidney’s voice in his ear, and Evgeni flinches away violently—what is Sidney doing, sitting so close? Why is he pressing their legs together like that? Why is he reaching for Evgeni’s hand where it’s resting on his thigh? “Hey, you okay? You seem a little rattled; do you need a breather, maybe someone to check you out?”

“Fuck off, what you do,” Evgeni hisses, snatching his hand away. “Don’t touch me, like, what are you, a faggot? Back off.”

Crosby freezes, and Letang peers around from his other side, eyes narrowed. “What the fuck did you just say to him?”

“You fuck off too,” Evgeni snaps, half-rising with his fists clenching in his gloves, and suddenly the bot maintenance guy has an iron grip on his arm.

“Cool it, or I’m taking you back and decommissioning you here and now instead of letting you get through this game and get examined,” Freddy snaps in his ear.

Evgeni shakes his head. There’s an odd echo in his ears, metallic and hollow, and snippets from his source code keep floating into his brain��Hockey Canada announced a plan to address "systemic issues" in the culture of hockey; the early history of hockey encouraged physical intimidation and control; oh, the good old hockey game....

The rest of the game is a blur. Evgeni doesn’t cause any more goals against, even manages to put up a primary assist on the power play, but he spends his time on the bench spacing out, shrinking away from anyone who tries to talk to him as he scrolls through his coding.

The diagnostics are all still fine. Something’s wrong, though.

Evgeni spent a year in stasis while his system was flooded with hockey history and hockey culture. He doesn’t remember it very well, but those first few years had aligned pretty well with what he’d learned—hockey was rough, hockey was physical, hockey was insular and conservative and macho.

Times change. So did Evgeni, through programming and his own conclusions drawn from observing the world around him.

He seesaws between past and present, software upgrades and personality patches warring in his motherboard until he thinks he might short out. He doesn’t, obviously; there are enough redundancies built into him to keep the ISS in orbit, let alone one android on an ice rink, but that doesn’t stop him from feeling overheated and dazed by the time they troop off the ice.

Instead of walking to the locker room he turns left, toward the bot maintenance room.

He half-hears a whispered argument behind him, and shortly after it cuts off someone hurries to catch up.

“Hey,” Sidney says, and Evgeni cringes, his words from earlier rattling in his skull like they were said by someone else.

“Sorry,” he grits out. He wants to reach out and take Sidney’s hand, but the thought of someone seeing him holding hands with a man fills him with nausea. “Not sure…”

“Yeah,” Sidney says. His voice is even, flat and unsettling, but Evgeni doesn’t have room to work through that and find a fix.

Freddy’s waiting outside the room with his arms crossed. He relaxes when Evgeni rounds into view, raising his eyebrows but not commenting when Sidney follows them into the room.

“Alright, let’s get you opened up and see what’s going on,” Freddy says, gesturing to the maintenance station.

It looks like a torture chamber, a metal chair surrounded by needles and machinery and a large, ominous machine with a screen and dozens of blinking lights. Evgeni gingerly lowers himself into the seat and closes his eyes, flinching a little when the chair lifts and tilts him forward, giving Freddy access to his control panel.

It doesn’t hurt to have his panel opened, but it feels wrong, invasive and intrusive. Evgeni used to need to get strapped into the chair to stop from fighting, but now he squeezes his eyes closed and bites on his tongue and takes some of the big, soothing breaths that do nothing for the functioning of his shell but seem to settle his mind anyway.

“Fuck,” Freddy murmurs, and Evgeni’s eyes fly open. Before he can say a word, Sidney’s at his side.

“What is it?” Sidney demands, resting a hand on Evgeni’s shoulder and rubbing his thumb soothingly as he leans over to peer into the panel. “Oh, shit.”

“What!” Evgeni demands, clenching his fists. He hates this, hates feeling helpless and paralyzed while people bend over his back and stare down into his innards.

“Not sure what happened in here, bud, but you’ve got some seriously fucked-up wires. Something in here burnt out, and a few of the metal casings are fried.” Freddy touches something inside Evgeni that sends his left knee straight out in a kick. “Yeah, damn, that’s no good. You were maybe a few days from catching on fire.”

Sidney’s hand spasms on Evgeni’s shoulder. “Can you fix him?” he asks, voice low and worried.

“Oh, sure,” Freddy says, and the easy confidence in his voice is reassuring. Freddy never sounds overwhelmed, never sounds like there’s something he can’t make work. “Might take a while, I think I’ll have to boot him into safety mode for a few hours to make sure everything’s connected okay, but he should be ready to go by Tuesday’s game.”

Sidney’s exhale is shaky with relief. Evgeni wants to reach up and touch his hand. “We start now?” he says instead, keeping his eyes on the ground.

“Sure thing. When was your last backup?” Freddy asks, rummaging through his toolkit. “Sid, when you head back can you let Sully know what’s going on, tell him I’ll get everyone a full rundown once I can pull the readout?”

“Sure. And he backed up last night, so you can probably just—”

Evgeni interrupts him. “No,” he says firmly, finally gathering the courage to crane his neck and look up at Sidney’s face. “Back up now, please. Want to remember what I say.”

“Good man,” Freddy says, clapping Evgeni on his other shoulder.

Sidney crouches down so he can look Evgeni in the eye. “You didn’t mean it,” he says quietly. His eyebrows are furrowed, and there’s a frown tugging at his mouth. He’s sad, Evgeni concludes, and hurt, and he’s trying to hide it. “I mean, it’s like…you’re hurt, you pulled something out from your coding, it’s not—”

“Sid,” Evgeni interrupts, and Sidney startles. A quirk in Evgeni’s programming is that he doesn’t use nicknames unless he really makes an effort. “Doesn’t matter why, I still say. Can’t forget I do, it’s not…” He thinks, running through the relationships course he downloaded back in 2015 when the team was struggling and Sidney seemed like he was on the verge of ending things. “It’s reason, not excuse. I still need, like, accountability.”

He mangles the word, but Sidney’s small smile is worth it.

—

Evgeni doesn’t dream, exactly. When he’s powered down there’s still a flicker of awareness as long as he has battery, enough to pull himself to wakefulness if there’s a threat, but extended downtime for repairs is like floating in a thick black cloud. There’s a very distance perception of voices, of movement and hands on his shell and wires being replaced, but nothing that Evgeni can actually truly call a memory as opposed to a superimposed expectation of what happened.

The grogginess when he’s powered back on is very real, though, as is the stiffness in his knees. He hopes he’ll have enough time to loosen up before he has to play.

“Welcome back,” Freddy’s cheerful voice booms, and Evgeni winces. “You should be set. Had you walk and sit and do a few jumping jacks yesterday in safety mode, nothing else loosened up or shorted. Okay—hands?”

He walks Evgeni through the post-repairs protocol, checking his reactivity, his senses, the last things he remembers to check his backup loaded correctly. Check, check, check.

When Evgeni stumbles out of the room, blinking against the harsh overhead lights in the hall, Sidney’s waiting for him.

“Hey,” Sidney says, eyes flickering over Evgeni’s face.

“I’m so sorry,” Evgeni says immediately. The shame that rolls through him is new and unexpectedly powerful—he rarely feels embarrassed, his programming doesn’t allow for him to make choices that lead to that. When it’s working correctly, of course. “God, Sidney, you know I don’t mean.”

“I know,” Sidney says, and the caution in his voice makes Evgeni’s chest ache. “I told Kris what happened, he said he won’t kick your ass unless it happens again.”

“I let him,” Evgeni says earnestly, which makes Sidney laugh. “Promise, I stand there, he kick and scratch and do whatever, I just let.”

He reaches forward tentatively, touching his fingers to the back of Sidney’s hand. The flood of relief when Sidney turns his hand up and laces their fingers together is nearly enough to make him lose his balance.

Emotions are tricky things, Evgeni thinks, but he wouldn’t wipe them for the world.