#job recruitment ads | Explore Tumblr posts and blogs

just-ornstein · 8 months ago

Text

[JK] My first job was as an Assistant Producer for a video game company called Interplay in Irvine, CA. I had recently graduated from Boston University's School of Fine Arts with an MFA in Directing (I started out as a theatre nerd), but also had some limited coding experience and a passion for computers. It didn't look like I'd be able to make a living directing plays, so I decided to combine entertainment and technology (before it was cool!) and pitched myself to Brian Fargo, Interplay's CEO. He gave me my first break. I packed up and moved out west, and I've been producing games ever since.

[JK] I loved my time at EA. I was there for almost a full decade, and learned a tremendous amount about game-making, and met the most talented and driven people, who I remain in touch with today. EA gave me many opportunities, and never stopped betting on me. I worked on The Sims for nearly 5 years, and then afterwards, I worked on console action games as part of the Visceral studio. I was the Creative Director for the 2007 game "The Simpsons", and was the Executive Producer and Creative Director for the 2009 game "Dante's Inferno".

[JK] I haven't played in a long while, but I do recall that after the game shipped, my wife and I played the retail version for some time -- we created ourselves, and experimented with having a baby ahead of the actual birth of our son (in 2007). Even though I'd been part of the development team, and understood deeply how the simulation worked, I was still continually surprised at how "real" our Sims felt, and how accurate their responses were to having a baby in the house. It really felt like "us"!

Now for some of the development and lore related questions:

[JK] So I ended up in the incredibly fortunate position of creating the shipping neighborhoods for The Sims 2, and recruiting a few teammates to help me as we went along.

Around the same time, we started using the Buy/Build tools to make houses we could save, and also bring them into each new build of the game (correcting for any bugs and incompatibilities). With the import tool, we could load Sims into these houses. In time, this "vanguard QA" process turned into a creative endeavor to define the "saved state" of the neighborhoods we would actually end up shipping with the game.

On playtesting & the leftover sims data on various lots:

Basically, we were in the late stages of development, and the Save Game functionality wasn't quite working. In order to test the game properly, you really needed to have a lot of assets, and a lot of Sims with histories (as if you'd been playing them for weeks) to test out everything the game had to offer. So I started defining a set of characters in a spreadsheet, with all their tuning variables, and worked with engineering to create an importer, so that with each new build, I could essentially "load" a kind of massive saved game, and quickly start playing and testing.

It was fairly organic, and as the game's functionality improved, so did our starter houses and families.

The thought process behind the creation of the iconic three neighborhoods:

I would not say it was particularly planned out ahead of time. We knew we needed a few saved houses to ship with the game; Sims 1, after all, had the Goth house, and Bob Newbie's house. But there wasn't necessarily a clear direction for what the neighborhood would be for Sims 2. We needed the game to be far enough along, so that the neighborhood could be a proper showcase for all the features in the game. With each new feature that turned alpha, I had a new tool in my toolbox, and I could expand the houses and families I was working on. Once we had the multi-neighborhood functionality, I decided we would not just have 1 starter neighborhood, but 3. With the Aging feature, Memories, a few wacky objects, plus a huge catalog of architectural and decorative content, I felt we had enough material for 3 truly distinct neighborhoods. And we added a couple of people to what became the "Neighborhood Team" around that time.

Later, when we created Strangetown, and eventually Veronaville, I believe we went back and changed Pleasantville to Pleasantview... because I liked the alliteration of "Verona-Ville", and there was no sense in having two "villes". (To this day, by the way, I still don't know whether to capitalize the "V" -- this was hotly debated at the time!)

Pleasantview:

Anyway, to answer your question, we of course started with Pleasantview. As I recall, we were not quite committed to multiple neighborhoods at first, and I think it was called Pleasantville initially, which was kind of a nod to Simsville... but without calling it Simsville, which was a little too on the nose. (There had also been an ill-fated game in development at Maxis at the time, called SimsVille, which was cancelled.) It's been suggested that Pleasantville referred to the movie, but I don't think I ever saw that movie, and we just felt that Pleasantville kind of captured the feeling of the game, and the relaxing, simple, idyllic world of the Sims.

Pleasantview started as a place to capture the aging feature, which was all new to The Sims 2. We knew we had toddlers, teens, and elders to play with, so we started making families that reflected the various stages of family life: the single mom with 3 young kids, the parents with two teens, the old rich guy with two young gold-diggers, etc. We also had a much greater variety of ethnicity to play with than Sims 1, and we had all new variables like sexual orientation and memories. All these things made for rich fodder for a great diversity of families. Then, once we had family trees, and tombstones that carried the actual data for the dead Sims, the doors really blew open. We started asking ourselves, "What if Bella and Mortimer Goth could be characters in Sims 2, but aged 25 years? And what if Cassandra is grown up? And what if Bella is actually missing, and that could be a fun mystery hanging over the whole game?" And then finally the "Big Life Moments" went into the game -- like weddings and birthdays -- and we could sort of tee these up in the Save Game, so that they would happen within the first few minutes of playing the families. This served both as a tutorial for the features, but also a great story-telling device.

Anyway, it all just flowed from there, as we started creating connections between families, relationships, histories, family trees, and stories that we could weave into the game, using only the simulation features that were available to us. It was a really fun and creative time, and we wrote all of the lore of Sims 2 within a couple of months, and then just brought it to life in the game.

Strangetown:

Strangetown was kind of a no-brainer. We needed an alternate neighborhood for all the paranormal stuff the Sims was known for: alien abduction, male pregnancy, science experiments, ghosts, etc. We had the desert terrain, which created a nice contrast to the lush Pleasantville, and gave it an obvious Area 51 vibe.

The fact that Veronaville is the oldest file probably reflects the fact that it was finished first, not that it was started first. That's my guess anyway. It was the simplest neighborhood, in many ways, and didn't have as much complexity in terms of features like staged big life moments, getting the abduction timing right, the alien DNA thing (which I think was somewhat buggy up until the end), etc. So it's possible that we simply had Veronaville "in the can", while we put the last polish on Pleasantville (which was the first and most important neighborhood, in terms of making a good impression) and Strangeville (which was tricky technically).

Veronaville:

But my personal favorite was Veronaville. We had this cool Tudor style collection in the Build mode catalog, and I wanted to ship some houses that showed off those assets. We also had the teen thing going on in the aging game, plus a lot of romance features, as well as enemies. I have always been a Shakespeare buff since graduate school, so putting all that together, I got the idea that our third neighborhood should be a modern-day telling of the Romeo and Juliet story. It was Montys and Capps (instead of Montagues and Capulets), and it just kind of wrote itself. We had fun creating the past family trees, where everyone had died young because they kept killing each other off in the ongoing vendetta.

[JK] You know, I have never seen The Lone Gunmen, and I don't remember making any kind of direct references with the Strangetown Sims, other than the general Area 51 theme, as you point out. Charles London helped out a lot with naming Sims, and I'm pretty sure we owe "Vidcund" and "Lazlo" to him ... though many team members pitched in creatively. He may have had something in mind, but for me, I largely went off of very generic and stereotypical ideas when crafting these neighborhoods. I kind of wanted them to be almost "groaners" ... they were meant to be tropes in every sense of the word. And then we snuck in some easter eggs. But largely, we were trying to create a completely original lore.

[JK] Well, I think we kind of pushed it with The Sims 2, to be honest, and I remember getting a little blow-back about Bunny Broke, for example. Bunny Broke was the original name for Brandi Broke. Not everyone found that funny, as I recall, and I can understand that. It must have been changed before we shipped.

We also almost shipped the first outwardly gay Sims in those neighborhoods, which was bold for EA back in 2004. My recollection was that we had set up the Dreamers to be gay (Dirk and Darren), but I'm looking back now and see that's not the case. So I'm either remembering incorrectly (probably) or something changed during development.

In general we just did things that we found funny and clever, and we just pulled from all the tropes of American life.

[JK] The alien abduction started in Sims 1, with a telescope object that was introduced in the "Livin' Large" expansion pack. That's when some of the wackier ideas got introduced into the Sims lore. That pack shipped just before I joined Maxis in 2001; when I got there, the team had shipped "House Party" and was underway on "Hot Date". So I couldn't tell you how the original idea came about, but The Sims had this 50's Americana vibe from the beginning, and UFOs kind of played right into that. So the alien abduction telescope was a no-brainer to bring back in Sims 2. The male pregnancy was a new twist on the Sims 1 telescope thing. It must have been that the new version (Sims 2) gave us the tech and flexibility to have male Sims become pregnant, so while this was turned "off" for the core game, we decided to take advantage of this and make a storyline out of it. I think this really grew out of the fact that we had aliens, and alien DNA, and so it was not complicated to pre-bake a baby that would come out as an alien when born. The idea of a bunch of guys living together, and then one gets abducted, impregnated, and then gives birth to an alien baby ... I mean, I think we just all thought that was hilarious, in a sit-com kind of way. Not sure there was much more to it than that. Everything usually came from the designers discovering ways to tweak and play with the tech, to get to funny outcomes.

[JK] Possibly we were just testing the functionality of the Wants/Fears and Memories systems throughout development, and some stuff got left over.

[JK] I can't remember, but that sounds like something we would have done! I'm pretty sure we laid the groundwork for more stories that we ended up delivering :) But The Sims 2 was a great foundation for a lot of continued lore that followed.

I once again want to thank Jonathan Knight for granting me this opportunity and taking the time from his busy schedule to answer my questions.

#BURNING LORE QUESTIONS FINALLY ANSWERED!! :D #the sims 2 #ts2 #sims 2 #ea games #ea #electronic arts #sims #the sims #strangetown #veronaville #pleasantview #jonathan knight interview #the sims 2 development #sims 2 development #sims 2 beta #I'm so glad I got this opportunity man.

1K notes · View notes

hospitalrecruiting · 2 years ago

Photo

Physician recruitment is a competitive market, so making standout job ads is important. Here are the 7 biggest things physicians want to see in a job description.

#physician #recruiter #recruitment #job ad #job board #job description #healthcare #career

0 notes

bloodyjuls-blog · 20 days ago

Text

NOTHING MUCH(Russo's sister X Leah Williamson)

Kay Russo had always been Alessia’s shadow. Since they were little girls, Alessia was the star of the family: the one who shined on the football field, the one who made her parents proud, the one who had a solid group of friends who seemed to want to crush anyone who didn’t fit into their perfect world. Kay, on the other hand, was “the other.” It wasn’t that she wasn’t talented; it just never seemed like enough.

As they grew up, the differences became more pronounced. Alessia had a clear path: Manchester United, the English national team, and eventually Arsenal. On the other hand, Kay was stuck in mediocre jobs and awful comments from her parents and sister. “Why can’t you be more like Alessia?” was a phrase she heard all too often.

The relationship between Kay and Alessia was tense, but the breaking point came one night, when Alessia, along with a group of her friends, began to make fun of Kay in front of everyone at a family gathering.

“And you, Kay?” “What have you been up to lately?” Alessia said with a venomous smile. “Did you find a job or are you still living off of mom and dad’s money?”

Laughter echoed around the room, and though Kay tried to keep her composure, she felt her stomach churn with shame. That night, locked in her room, Kay collapsed on her bed with her eyes filled with tears. She knew she had to change something in her life and escape that toxic dynamic. It was then that while surfing the internet, she saw an ad for the Royal Navy: “Find a purpose. Discover your potential. Join the Royal Navy.”

Kay didn’t think twice. She knew that enlisting was her ticket out, but she also knew that her family would never understand. So she made a drastic decision: she didn’t tell them anything. The following week, the recruitment process began.

A few weeks later, Kay received confirmation: she had been accepted. The date to report was marked on her calendar, and as it approached, she felt a mix of nerves and relief. One night before she left, she decided she should at least tell her family something, but not everything.

“I’m leaving tomorrow, I’ll be gone for a while,” she said over dinner.

Her mother looked up from her plate with disdain.

“On vacation? With what money?” she asked sarcastically.

Kay took a deep breath, trying not to lose her cool. “Never mind, I just wanted to let them know.”

Alessia laughed softly and murmured, “Always so mysterious.”

Kay gritted her teeth, finishing her meal in silence. That would be the last dinner she would share with them for a long time.

The day Kay left, she left home early, carrying a backpack and leaving behind a short note on the kitchen table: “I’m gone. I don’t know when I’ll be back. Take care of yourselves.”

The months that followed were a whirlwind. Basic training in the Royal Navy was brutal, but Kay held on to it with determination. Every physical exercise, every lesson, every grueling hour felt like a step toward freedom. Here she wasn't "Alessia's sister," she didn't have to endure her family's hurtful comments. Here she was simply Kay, someone trying hard to find her place.

After completing her training, Kay was given her first leave. She decided to return home, even though she knew it would be difficult.

When she arrived, the reception was cold. Alessia wasn’t even there; she was away on a trip with her team. Her parents barely showed any interest in hearing about her experience in the Navy.

“So what’s next?” her father asked in an indifferent tone. “Are you going to be here long?”

Kay felt the knot in her chest grow bigger. That night, as Alessia posted pictures on Instagram with her teammates, Kay sat alone in the backyard, wondering if she would ever truly belong in this family.

It was during one of those visits home that Kay met Leah Williamson. Alessia had invited some of her teammates over for dinner, and though Kay tried to stay out of the way, she couldn’t help but run into them. Leah was kind, something Kay hadn’t expected. They had a brief but meaningful conversation, and in that moment, Kay felt something she hadn’t felt in a long time: connection.

Kay returned to her base after that brief visit home. The experience only reinforced what she already knew: her family would not change. But one thing remained in her mind: Leah Williamson. They had exchanged a few words over dinner, but there was something about her warmth, the way she seemed to see Kay as a person, and not as a shadow of Alessia. Leah didn’t know her, she was unprejudiced, and that made her different.

The day Kay had her first chance to visit London while on leave, she remembered that Leah was playing for Arsenal. She decided to take a chance and attend a match. It was strange to be surrounded by thousands of fans excited about something that, until recently, had been a source of insecurity for her: football and the shadow of her sister. Alessia was not on the team yet, which made the experience a little more bearable.

After the match, Leah, who had played spectacularly, was surrounded by fans and media. Kay watched her from a distance, trying to convince herself that she would simply leave without saying anything. But Leah saw her.

“Kay!” she called from the field, waving excitedly.

Kay froze for a moment before shyly approaching.

“What are you doing here babe?” Leah asked, clearly surprised but pleased.

Kay shrugged, trying not to look nervous. “I was in town and thought I’d come to watch the game.”

Leah smiled, and something in her expression made Kay feel less invisible. “I’m glad you came. Do you have plans now?”

Before she could stop herself, Kay shook her head. That night, they ended up having dinner together at a small, low-key restaurant near the stadium. It was the start of something unexpected.

As the months passed, Kay’s visits to London became more frequent. She always found an excuse to see her, and Leah seemed to enjoy her company as much as she enjoyed Leah’s. They talked about everything: life in the Navy, the challenges of being a professional soccer player, and, occasionally, Kay’s family struggles.

One night, as they walked through the quiet streets of London after dinner, Leah stopped and looked at her seriously.

“Kay, why don’t you ever talk about Alessia much? I know you are sisters, but you almost seem to avoid mentioning her.”

Kay looked at the ground, feeling her chest tighten. Talking about Alessia was like opening a wound that never healed.

“It’s complicated, Leah. I’ve always been… different to them. Alessia’s the star, the one who shines. I… I just exist on the periphery.”

Leah took her hand, an unexpected but comforting gesture. “That’s not fair, Kay. You shouldn’t feel that way.”

Kay looked up, surprised by Leah’s sincerity. It was at that moment that she knew this connection was something special.

As her relationship with Leah grew stronger, Kay knew there would be trouble sooner or later. Leah was a public figure, and although she hadn��t revealed details of her personal life to the world, speculation was constant. The Arsenal team was full of rumors about who Leah’s partner could be, but no one suspected Kay. Alessia, still playing in Manchester, had no idea that her younger sister was getting so close to one of her friends.

Kay also knew that her family wouldn’t approve of the relationship, not only because of who Leah was, but because the idea that she could have anything valuable in her life seemed inconceivable to them.

Everything changed when Kay received the news of a new deployment abroad. It was a high-risk mission, and although she was used to challenges, this time was different. Now she had something to lose. When she told Leah, the reaction was immediate.

“How long will you be gone honey?” Leah asked, trying to remain calm.

“I don’t know but it could be months.” Leah nodded and cuddled her, but Kay could see the worry in her eyes. That night, as they said goodbye, Leah hugged her tighter than usual.

“Just promise me you’ll come back, okay?”

Kay didn’t answer, because she knew that was a promise she couldn’t guarantee.

During deployment, Kay was severely wounded in an ambush. The bullet that hit her back damaged her spine, leaving her paralyzed from the waist down. Doctors told her she would never walk again. The physical pain was immense, but the emotional blow was even worse.

When she was finally able to reach Leah from the military hospital, the conversation was brief but full of emotion.

“I’m alive,” was the first thing Kay said, her voice shaking.

Leah, on the other end of the line, let out a sigh of relief, but she couldn’t hide her worry. “What happened, Kay? Tell me the truth.”

Kay closed her eyes, feeling the tears begin to flow. “I’m in a wheelchair, Leah.” I don’t know what’s going to happen to me.

The silence on the other end of the line was painful, but when Leah finally spoke, her voice was firm. “I’m going to be with you, Kay. No matter what.”

Kay spent weeks in the military hospital, facing the reality of her condition. Doctors stabilized her, but the words she most feared hearing finally came: she would never walk again. She wasn’t ready to face it. Her life as she knew it had changed forever. The military, her only refuge, was also out of reach.

London became her next destination. The medical staff recommended that she be transferred to a civilian hospital where she could receive specialized treatment and subsequently begin the rehabilitation process. When Kay thought about where she could stay afterward, only one person came to mind: Leah.

Leah waited for Kay at Heathrow Airport, visibly worried. Even though she had received constant updates about her condition, seeing her in person would be an emotional challenge. When Kay appeared in the wheelchair, pushed by a hospital attendant, Leah felt her heart tighten in her chest.

Kay wore a stoic expression as if she was using all her strength to keep her emotions in check. Leah could see past that, though. Kay’s eyes, once full of life, now reflected exhaustion and pain.

“Hi my love" Kay said quietly as she came to her side.

Leah leaned in to hug her, ignoring the fact that they were in the middle of a crowded airport. It was a long hug, one they both needed.

“Welcome home baby,” Leah said softly leaning against her and kiss her deeply.

Kay wanted to correct her, reminding her that London wasn’t her home, but she couldn’t find the words. Maybe, after all, Leah was the closest thing she had to a home.

Leah’s London flat was cozy but small, and the modifications needed to accommodate the wheelchair made the space feel even more cramped. Leah had worked tirelessly to get everything ready, installing ramps and rearranging furniture. Kay felt grateful, but also deeply uncomfortable.

“You didn’t have to do all this, Le” Kay said as she scanned the space with difficulty.

Leah, who was making a cup of tea, turned to her with a calm smile. “Of course I did. I wasn’t going to let you go through this alone.”

Kay nodded, but inside, guilt and frustration were growing. She wasn’t used to depending on anyone, let alone someone as important to her as Leah.

The first few weeks were a mix of intense emotions. Kay tried to keep a routine, attending physical therapy sessions and learning to adjust to her new life. However, every little failure—not being able to reach something, needing help with simple tasks—felt like a monumental defeat.

One night, while Leah was cooking, Kay decided it was time to talk about what had happened at the military hospital. It was a weight she had carried alone for far too long.

“Leah, can you sit down for a moment?”

Leah stopped what she was doing and sat across from Kay in the living room. The concern on her face was evident.

“What’s wrong, Kay?”

Kay took a deep breath, her hands shaking slightly. “There’s something I need to tell you about what they did to me in the Navy before all the injuries happened.”

Leah nodded, her expression becoming more serious. “I’m listening.”

Kay began to speak, her voice shaky at first, but gaining strength as she went on. She told him about the treatments she’d endured: the electroshocks they justified as “experimental therapy,” the times they’d left her alone for hours without help, and the “rehab” sessions that often included pushing her physically to the limit.

“There were days I thought… I wasn’t going to get out of there. They yelled at me that I needed to be strong, that if I couldn’t take it, I didn’t deserve to be in the military.”

Leah clenched her fists as she listened, her face reflecting a mix of anger and sadness.

“How could they do that to you?” she finally asked, her voice cracking.

“It’s the price of being weak in their world, Leah. They couldn’t stand someone like me not being “useful” anymore.”

Leah leaned forward, taking Kay’s hands in hers. “Listen to me, Kay. What they did was inhumane, and you have nothing to be ashamed of. You are one of the strongest people I know.”

The tears Kay had been holding back finally began to fall. Leah didn’t say anything else, she held her, allowing her to release all the pain she had built up over the months.

Alessia’s arrival at Arsenal added a new layer of tension to Kay’s life. Although both had avoided any confrontation, Alessia’s passive-aggressive comments were quick to appear.

One afternoon, while Leah and Kay were at home, Alessia arrived unannounced. Leah had forgotten to lock her door, and Alessia walked in like she owned the place.

“So this is where you’re hiding, Kay?” Alessia said, with a sarcastic smile as she looked around the apartment.

Leah, who was in the kitchen, quickly came out upon hearing Alessia’s tone. “What are you doing here, Alessia?”

“I just wanted to see how my long-lost sister lived. It seems you’ve been busy… or should I say ‘well-kept’?”

Kay, who was in the living room, turned to face Alessia. “What do you want, Alessia?”

“I want to understand how you went from being a ghost to… this.” She pointed at Leah with a nod.

Leah, clearly upset, stepped in. “Alessia, if you come here to cause trouble, you can leave.”

The exchange escalated, and Kay felt old wounds reopening. Alessia had always known how to touch her weak spots, and Leah was caught in the middle. Eventually, Leah had to ask Alessia to leave, leaving Kay emotionally drained.

Despite the conflicts, the relationship between Kay and Leah continued to grow stronger. The emotional connection they shared was evident, and small displays of affection—a hand on the shoulder, an unexpected hug—began to evolve into something more.

One night, while watching a movie together, Leah leaned slightly toward Kay, resting her head on her shoulder. Kay, surprised at first, allowed the gesture and smiled.

It was a small moment of intimacy, but to Kay, it meant more than Leah could ever imagine.

Winter had come to the city, and with it, the streets of London were filled with Christmas lights and decorations. Kay, however, barely noticed the festivities. Her days were divided between physical therapy, medical adjustments, and increasingly intimate moments with Leah. However, the conflict with Alessia and the memories of the abuse at the military compound weighed on her like a constant shadow.

One morning, as Kay tried to adjust to the new exercise routine her physical therapist had recommended, Leah received an unexpected text from Alessia. She wanted to “talk.”

“Is it a good idea to give her space after what happened here?” Kay asked from her spot in the living room, as Leah checked the message.

Leah sighed, leaving her phone on the table. “I think it’s not just you, Kay. Alessia… she has issues to work out with herself.”

Kay raised an eyebrow. “Don’t justify what she does. She’s always found ways to make me feel like I’m worthless.” Leah walked over and knelt in front of Kay, placing her hands over hers. “No one has the right to make you feel that way. Not even Alessia.”

Kay wanted to believe her, but the years of emotional abuse she had endured were not easy to forget.

That afternoon, Leah went to Arsenal Stadium to meet Alessia after training. Alessia, who had been in a bad mood all day, was quick to spill the beans.

“What the hell are you doing with Kay?” Alessia asked bluntly as Leah closed the door to the meeting room.

Leah, trying to remain calm, replied, “I’m looking out for her. Something no one else is doing.”

“Looking out?” Alessia let out a sarcastic laugh. “Since when do you need to play savior?”

Leah frowned. “This isn’t a game, Alessia.” Kay has been through things that neither you nor I can imagine, and instead of supporting her, you--

“Don’t lecture me!” Alessia interrupted, slamming her hands on the table. “Kay has always been a burden. Every time I tried to stand out, she was there, ruining everything.”

Leah felt her patience wearing thin. “You know what ruins everything, Alessia? Your inability to see her as anything more than a reflection of your insecurities.”

The silence that followed was deafening. Alessia hadn’t expected such a direct response, and for a moment, she didn’t know what to say.

“This isn’t over, Leah,” she finally said, before leaving the room.

That night, Leah returned to the apartment emotionally drained. Kay noticed her expression and decided it was time to share something she had been holding back.

“What happened?” Kay asked as Leah plopped down on the couch next to her.

“Your sister… doesn’t understand anything,” Leah replied, massaging her temples.

Kay sighed and looked out the window. “It’s because she’s never seen me as her sister, Leah. I was always ‘the other Russo.’ The one with no talent. The one who didn’t fit in.”

Leah turned to her, surprised by the tone of vulnerability in her voice.

“You want to know why I joined the Royal Navy?” Kay asked, her voice shaking slightly.

Leah nodded, knowing Kay needed to vent.

“I saw an ad online while I was looking for a job. It seemed like a way to escape everything… from Alessia, from my family, from myself. I wanted to prove that I could do something for myself, something that no one could take away from me.”

Kay paused, her hands shaking as she recalled those days.

“But even then… it was never enough. And then… then came the hospital.”

Leah took her hand, giving it a gentle but firm squeeze. “You don’t have to tell me if you’re not ready.”

Kay shook her head. “I need to. Because if I don’t, those things are going to keep haunting me.”

Then, Kay began to speak, detailing the horrors she had endured. She described the time when she had arrived at the hospital very badly injured thinking that what had happened was her fault, or that it was all karma for being fragile and not facing things, where she would rather a thousand times have her die than have a partner who had a family that loved him.

“There was a doctor… I will never forget her face.” She told me I was a failure, that someone in a wheelchair was nothing anymore, that I was wasting valuable Navy resources that could be used on soldiers who would go back into combat, I… I can’t take it anymore.” Kay paused, taking a deep breath.

Leah hugged her tightly, unable to hold back her tears. “God, Kay… I can’t imagine what you’ve been through.”

“I don’t want you to see me as a victim, Leah.” Kay rested her forehead on Leah’s shoulder. “I just want to be someone who deserves… something.”

“You deserve everything, Kay. And I’m here to remind you of that every day.”

Despite everything, Kay began to find small moments of peace in her life with Leah. They began to spend more time together, sharing stories and laughing despite the circumstances.

One night, as Leah read a book on the couch, Kay leaned into her, resting her head on her shoulder. Leah smiled and set the book aside, putting an arm around Kay.

“You know?” —Leah said after a while. —I never thought I'd find someone I wanted to share so much with.

Kay looked up, surprised by the confession. —And me?

—You're that person, Kay. My person, my forever.

For the first time in a long time, Kay felt like maybe, just maybe, she had a place in the world where she truly belonged.

#woso #woso x reader #lionesses #woso imagines #woso community #leah williamson x reader #leah williamson imagine #leah williamson #alessiarusso #alessia russo x reader #alessia russo imagine #alessia russo #woso one shot #woso imagine #arsenal wfc imagines #arsenal x reader #lionesses x reader

324 notes · View notes

newspaper-advertisement · 1 year ago

Text

Book your HT Shine Ads with Hindustan Times Instantly Online

#ht shine ads #ht shine advertisement #hindustan times shine ads #ht shine jobs advertisement #display advertising in HT Shine #display ads in HT Shine #book display ads in HT Shine #publish recruitment adverts in Shine

0 notes

mostlysignssomeportents · 2 months ago

Text

Reverse engineers bust sleazy gig work platform

If you'd like an essay-formatted version of this post to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:

https://pluralistic.net/2024/11/23/hack-the-class-war/#robo-boss

A COMPUTER CAN NEVER BE HELD ACCOUNTABLE

THEREFORE A COMPUTER MUST NEVER MAKE A MANAGEMENT DECISION

Supposedly, these lines were included in a 1979 internal presentation at IBM; screenshots of them routinely go viral:

https://twitter.com/SwiftOnSecurity/status/1385565737167724545?lang=en

The reason for their newfound popularity is obvious: the rise and rise of algorithmic management tools, in which your boss is an app. That IBM slide is right: turning an app into your boss allows your actual boss to create an "accountability sink" in which there is no obvious way to blame a human or even a company for your maltreatment:

https://profilebooks.com/work/the-unaccountability-machine/

App-based management-by-bossware treats the bug identified by the unknown author of that IBM slide into a feature. When an app is your boss, it can force you to scab:

https://pluralistic.net/2023/07/30/computer-says-scab/#instawork

Or it can steal your wages:

https://pluralistic.net/2023/04/12/algorithmic-wage-discrimination/#fishers-of-men

But tech giveth and tech taketh away. Digital technology is infinitely flexible: the program that spies on you can be defeated by another program that defeats spying. Every time your algorithmic boss hacks you, you can hack your boss back:

https://pluralistic.net/2022/12/02/not-what-it-does/#who-it-does-it-to

Technologists and labor organizers need one another. Even the most precarious and abused workers can team up with hackers to disenshittify their robo-bosses:

https://pluralistic.net/2021/07/08/tuyul-apps/#gojek

For every abuse technology brings to the workplace, there is a liberating use of technology that workers unleash by seizing the means of computation:

https://pluralistic.net/2024/01/13/solidarity-forever/#tech-unions

One tech-savvy group on the cutting edge of dismantling the Torment Nexus is Algorithms Exposed, a tiny, scrappy group of EU hacker/academics who recruit volunteers to reverse engineer and modify the algorithms that rule our lives as workers and as customers:

https://pluralistic.net/2022/12/10/e2e/#the-censors-pen

Algorithms Exposed have an admirable supply of seemingly boundless energy. Every time I check in with them, I learn that they've spun out yet another special-purpose subgroup. Today, I learned about Reversing Works, a hacking team that reverse engineers gig work apps, revealing corporate wrongdoing that leads to multimillion euro fines for especially sleazy companies.

One such company is Foodinho, an Italian subsidiary of the Spanish food delivery company Glovo. Foodinho/Glovo has been in the crosshairs of Italian labor enforcers since before the pandemic, racking up millions in fines – first for failing to file the proper privacy paperwork disclosing the nature of the data processing in the app that Foodinho riders use to book jobs. Then, after the Italian data commission investigated Foodinho, the company attracted new, much larger fines for its out-of-control surveillance conduct.

As all of this was underway, Reversing Works was conducting its own research into Glovo/Foodinho's app, running it on a simulated Android handset inside a PC so they could peer into app's data collection and processing. They discovered a nightmarish world of pervasive, illegal worker surveillance, and published their findings a year ago in November, 2023:

https://www.etui.org/sites/default/files/2023-10/Exercising%20workers%20rights%20in%20algorithmic%20management%20systems_Lessons%20learned%20from%20the%20Glovo-Foodinho%20digital%20labour%20platform%20case_2023.pdf

That report reveals all kinds of extremely illegal behavior. Glovo/Foodinho makes its riders' data accessible across national borders, so Glovo managers outside of Italy can access fine-grained surveillance information and sensitive personal information – a major data protection no-no.

Worse, Glovo's app embeds trackers from a huge number of other tech platforms (for chat, analytics, and more), making it impossible for the company to account for all the ways that its riders' data is collected – again, a requirement under Italian and EU data protection law.

All this data collection continues even when riders have clocked out for the day – its as though your boss followed you home after quitting time and spied on you.

The research also revealed evidence of a secretive worker scoring system that ranked workers based on undisclosed criteria and reserved the best jobs for workers with high scores. This kind of thing is pervasive in algorithmic management, from gig work to Youtube and Tiktok, where performers' videos are routinely suppressed because they crossed some undisclosed line. When an app is your boss, your every paycheck is docked because you violated a policy you're not allowed to know about, because if you knew why your boss was giving you shitty jobs, or refusing to show the video you spent thousands of dollars making to the subscribers who asked to see it, then maybe you could figure out how to keep your boss from detecting your rulebreaking next time.

All this data-collection and processing is bad enough, but what makes it all a thousand times worse is Glovo's data retention policy – they're storing this data on their workers for four years after the worker leaves their employ. That means that mountains of sensitive, potentially ruinous data on gig workers is just lying around, waiting to be stolen by the next hacker that breaks into the company's servers.

Reversing Works's report made quite a splash. A year after its publication, the Italian data protection agency fined Glovo another 5 million euros and ordered them to cut this shit out:

https://reversing.works/posts/2024/11/press-release-reversing.works-investigation-exposes-glovos-data-privacy-violations-marking-a-milestone-for-worker-rights-and-technology-accountability/

As the report points out, Italy is extremely well set up to defend workers' rights from this kind of bossware abuse. Not only do Italian enforcers have all the privacy tools created by the GDPR, the EU's flagship privacy regulation – they also have the benefit of Italy's 1970 Workers' Statute. The Workers Statute is a visionary piece of legislation that protects workers from automated management practices. Combined with later privacy regulation, it gave Italy's data regulators sweeping powers to defend Italian workers, like Glovo's riders.

Italy is also a leader in recognizing gig workers as de facto employees, despite the tissue-thin pretense that adding an app to your employment means that you aren't entitled to any labor protections. In the case of Glovo, the fine-grained surveillance and reputation scoring were deemed proof that Glovo was employer to its riders.

Reversing Works' report is a fascinating read, especially the sections detailing how the researchers recruited a Glovo rider who allowed them to log in to Glovo's platform on their account.

As Reversing Works points out, this bottom-up approach – where apps are subjected to technical analysis – has real potential for labor organizations seeking to protect workers. Their report established multiple grounds on which a union could seek to hold an abusive employer to account.

But this bottom-up approach also holds out the potential for developing direct-action tools that let workers flex their power, by modifying apps, or coordinating their actions to wring concessions out of their bosses.

After all, the whole reason for the gig economy is to slash wage-bills, by transforming workers into contractors, and by eliminating managers in favor of algorithms. This leaves companies extremely vulnerable, because when workers come together to exercise power, their employer can't rely on middle managers to pressure workers, deal with irate customers, or step in to fill the gap themselves:

https://projects.itforchange.net/state-of-big-tech/changing-dynamics-of-labor-and-capital/

Only by seizing the means of computation, workers and organized labor can turn the tables on bossware – both by directly altering the conditions of their employment, and by producing the evidence and tools that regulators can use to force employers to make those alterations permanent.

Image: EFF (modified) https://www.eff.org/files/issues/eu-flag-11_1.png

CC BY 3.0 http://creativecommons.org/licenses/by/3.0/us/

#pluralistic #etui #glovo #foodinho #alogrithms exposed #reverse engineering #platform work directive #eu #data protection #algorithmic management #gdpr #privacy #labor #union busting #tracking exposed #reversing works #adversarial interoperability #comcom #bossware

345 notes · View notes