#code team

[agentredfort]

Blacker and Ruby 100% have a secret handshake that lasts at least thirty seconds and they do this in front of hitch Froghorn AND lb, no one can figure out how they remember it (it changes everytime??) or why the actual Sam Hill they do it

the secret handshake is actually based on a logarithmic sequence that they both happen to have memorized. because they’re nerds like that

[trauma-13]

Oh well.

[blackers-donuts]

Silence Is Golden

So a lovely anon wanted a coding team fic so I wrote one about Ruby burying her hatchet with Froghorn.

There was a sharp knock at the door. Ruby was finally going to bury the hatchet with Froghorn by asking him for help. Okay, she had already tried to find Blacker, Blacker was nowhere to be seen, she knew Hitch was definitely more of a field agent and the way he stared at the paper only proved it. So last on the list of people she could bother without being fired is Froghorn and if she wanted to continue decoding at spectrum. Let’s just say they were bound to either hate each other forever or become vague acquaintances.

“Come in,” he says, “hello Agent Redfort.” He says her name with a sneer she understands, the same sneer Clancy’s french teacher gave him when he said the wrong form of aller. “Agent Froghorn, can I have some help,” she says before adding another word of “please.”

Froghorn looks up from his desk, “you sure as hell ain’t Bradley Baker.” “I did find him though so, I basically am,” she replies, “I couldn’t find Agent Blacker coz I know you don’t like being disturbed and then. I don’t know anyone else.” Froghorn smiles, “always happy to help Redfort. I just don’t like being randomly disturbed.” “I get that sometimes Del gets really loud and I can’t concentrate,” she blurts. “You’re doing that now Redfort, now let’s see the code.”

They sit down and whilst Froghorn at first starts working in a silenced rush once Blacker arrives and starts to show the teenager how they are working the code out, carefully wording how they are not experimenting with stuff they know won’t work. It all fits each person contributing to the completion of the code, a little suggestion here or there from Ruby whilst Blacker and Froghorn work on it. “There you go agent Redfort, glad to be of assistance,” says Froghorn pushing his hair back, it flops forwards depending on how warm it is.

There is another knock on the door and Hitch walks in. “Could you give that to LB, I don’t want to take credit for your work,” she says, they had finished a few minutes ago and now were just sitting there, talking about other codes they had either created or solved. Froghorn smiles, in the awkward way he always acts when someone he doesn’t like does something unnecessarily nice. “Couldn’t have done it without you.” He says. So Blacker picks it up confirms that he’ll tell LB who worked on it. Hitch stares at the current pair now working on a new code, Ruby was testing Froghorn on some code she had created when she was younger.

“I’ll pick you up later then kiddo, see you Froghorn,” says Hitch, holding the door open for Blacker.

Blacker walks back in, suddenly with donuts and coffee from somewhere. Presumably the cafeteria. He passes a donut to Ruby and places the coffee in front of Blacker and sits at the desk in the corner working on his own code.

Someone passes a new code to Ruby and now Froghorn had helped her discover the key she sits on the floor happily decoding the messages and Froghorn works on whatever he was working on before.

“Ruby, we have to head home now,” says Hitch once he had been granted access by Froghorn saying yes through the door. Ruby collects the file, puts it in her backpack. “Thanks Agent Froghorn, couldn’t have done it without you,” she says. Froghorn nods, “you’re welcome anytime Redfort. Anytime.”

The next time she couldn’t find anyone so heads to Froghorn’s to see if she can work with him. Just in quiet, just for the company. “Come in,” he says. Ruby walks in, “do you mind if I work in the corner please?” “Just be quiet Redfort,” he orders, “Blacker’s desk is clean.” She takes it as a yes. They sit in comfort till it is time for them to leave, Ruby had maths homework to breeze through and Hitch was done for the day. “You don’t need to knock Redfort, it just knocks me out of my zone,” says Froghorn.

The next time she just walks in, spots the beanbag now placed in the corner and sits there. She sees Blacker lift his head in acknowledgment and nudge Froghorn’s ankle, “hey Redfort.” “Hey guys, you don’t mind,” she asks. “Your beanbag Redfort, I brought it in foe you,” he says.

Ruby smiles and works, following the advice previously given to her. Eventually Blacker leaves, they continue to work now the careless mutters under Blacker’s breath was gone and they were concentrating fully on their codes. “Redfort, lock up once your done,” says Froghorn, “don’t touch the desk.” She gets tossed the keys and Froghorn leaves.

Now the silence is disconcerting for Ruby. At least with Froghorn their was his breath and occasional tapping of feet that created a noise but not silence like this. Let’s just say, she was glad when Hitch arrived.

“Froghorn just left you?” He asks on the way home. “Yeah, gave me the key and everything. I think we’re alright now,” says Ruby. Hitch shrugs, “whatever you think kiddo.” Ruby looks at him and he laughs, “of course Froghorn likes you.” Ruby smiles and goes to sleep in the seat next to him.

She walks in the next day and passes a paper bag to Froghorn, it contained the last donut that Clancy had given her. He thanks her and continues working, she sits down accepts Blacker’s donut and works. She locks up at the end of the day, and that’s how they end up working.

One day she was in early, it was summer vacation and the parents were away. “Hey Ruby, why are you waiting in the corridor,” asks Blacker. She shrugs and stands up collecting the hoodie from the floor, “no one was in.” “Redfort, what are you waiting for?” Froghorn yells from the corridor, “you have a key.” Ruby smiles, “it is your office, not mine.” “Thats nice of you Ruby, come on in,” says Froghorn. He holds the door open for the pair and they sit down and start to work, like previous days.

[gomerblogworld]

Read more: http://bit.ly/2W6Bfnx

Breaking: Code Team Pushes tPA to Lyse Clogged Toilet

https://gomerblog.com/wp-content/uploads/2014/03/iStock_000017519261Small-e1499857396907.jpg

DURHAM, NC - Acknowledging they were within the 4.5-hour window since symptom onset and had no other clear alternatives, a Code Team at Duke University Hospital pushed tPA in the hopes of lysing the clogged staff bathroom on the fifth floor. "Things looked dire.  Nurses, doctors on the floor t...

Read more on https://gomerblog.com/2019/04/tpa-clogged-toilet/?utm_source=TR&utm_campaign=DIRECT

www.gomerblog.com

[gomerblogworld]

Read more: http://bit.ly/2h5nBAQ

Code Team Performs Ill-Timed Mannequin Challenge During CPR

http://gomerblog.com/wp-content/uploads/2016/12/31021855_m.jpg

JACKSONVILLE, FL - A code team at Jacksonville Medical Center (JMC) is under investigation after an ill-timed Mannequin Challenge during a cardiac arrest went viral but left a patient in critical condition. "If there is one thing we cannot believe more than performing a Mannequin...

Read more on http://gomerblog.com/2016/12/mannequin-challenge/?utm_source=TR&utm_campaign=DIRECT

www.gomerblog.com

[podmedic]

Hospital Rapid Response Teams Save Lives

Hospital Rapid Response Teams Save Lives

So are you part of your hospital system’s rapid response or code team? I found a great article over at LiveScience.com that looks at rapid response teams and their effectiveness at improving mortality rates for acute conditions like myocardial infarction and stroke. As they say, detecting and treating patients before they go in to cardiac arrest is the key to improving patient outcomes.

Nurses…

View On WordPress

[jacksanity]

The hardest part about using this engine is it's connection between visuals and code. A lot of the time states on the cards (animations, locations, and other transitions) have to be manually altered by the GooCreate team and then implemented by the code team. This brings about all kinds of issues as the states aren't always correct when being placed into the game code. This is a very annoying aspect and I do not like having to expend several hours just on these issues as they will not be allowed the time we are devoting to them in our next phase of the game project.

The top image displays states going to locations that are incorrect and rotations that are incorrect, although they can be fixed it is really tedious to code whilst they are like this.

The bottom two images display the same thing but in the hand cards, where states are on the same z axis (in picture to the left) you can see through half of one card and half of the other as they compete for the same plane of view. The right just shows the cards out of scale when states are not reverted correctly.