Marilyn P. Perkins

Marilyn P. Perkins "Join 'Reddit Moral Stories,' where we explore the most compelling AITA dilemmas.

Share your insights, debate with others, and uncover the nuances of ethical decisions."

06/17/2026

I picked up the T-handle torque calibration wrench from the metal testing tray.

I set the mechanical dial to exactly three Newton-meters.

I fitted the driver head into the titanium implant screw.

I turned the heavy metal handle until it clicked sharply in the quiet lab.

That single click meant the strict torque specification was met.

I am a biomedical engineer working in the hospital's dedicated device development unit.

I design and build the internal hardware that replaces failing human joints.

My primary focus for the last three years has been a device called the ReJoint-S.

It is a reconstructed prosthetic shoulder joint featuring a complex three-axis articulation mechanism.

Most standard shoulder implants rely on a simple ball-and-socket design that severely limits mobility.

I engineered the ReJoint-S with a specialized titanium alloy shell to solve that exact problem.

The new material and the three-axis movement are designed to reduce implant rejection by forty-seven percent.

Every physical measurement in the lab must be absolutely perfect.

The FDA submission process requires an exhaustive design history file for any new medical hardware.

That file must explicitly name the responsible engineer for the device.

Without a complete engineering log, a medical device cannot even enter the regulatory review pipeline.

I spent three years documenting every single structural failure and every slight adjustment to the titanium shell.

I recorded every successful torque test.

The device development unit is a busy laboratory shared across five different biomedical engineers.

Tools migrate between workbenches constantly during the intensive prototyping phases.

I label all my specific calibration instruments with my initials, N.K., using a black medical-grade marker.

Every calibration tool must be strictly traceable to the exact engineer who last set the tension parameters.

After the wrench clicked today, I opened my primary engineering log.

The heavy binder was officially labeled BPD-ENG-2021-007.

I uncapped my pen and wrote the final entry.

Calibration four hundred, three Newton-meters, implant screw torque verified.

I signed my name at the bottom of the page as the responsible engineer.

Four hundred precise calibrations meticulously documented over three full years.

The prosthetic device was finally ready for the clinical trial phase.

Dr. Sean Park is the Head of Clinical Research at the hospital.

We have been partners for six years.

As the head of his division, Sean controls the hospital's grant pipeline and public research profile.

His department brings in the massive funding that keeps the institution running.

Four years ago, he stood in my testing lab on the day I finished the first physical prototype.

Before the engineering log existed, he picked up the heavy titanium joint.

He turned the three-axis mechanism over in his bare hands.

"This is completely different from anything currently on the surgical market," he said.

"When I look at the articulation range, I see a fundamental shift in the geometry."

"That is incredible work."

"It is a three-axis design," I replied.

"It closely matches the natural shoulder's movement envelope."

"If the forty-seven percent rejection rate holds in the clinical trial," he told me, "this entirely changes the standard of care."

"That is the engineering plan," I said.

He carefully set the prototype back down on the testing tray.

He was absolutely right about the clinical potential of the joint.

He had always understood exactly what my engineering could achieve for the patients.

That private conversation happened long before the official announcements and the hospital press releases.

This morning, the hospital hosted its annual medical conference.

The main auditorium was packed with six hundred orthopedic surgeons and representatives from the medical press.

I sat in the middle rows of the audience.

My printed conference badge listed me simply as device development unit staff.

The massive room smelled like expensive catering coffee and dry air conditioning.

Sean stood at the main podium under the bright stage lights.

He wore a tailored suit and held a presentation remote.

The massive projection screen behind him displayed the ReJoint-S prosthetic shoulder.

The audience of six hundred surgeons fell completely silent.

I watched the medical press representatives taking rapid notes in the front row.

Several prominent orthopedic surgeons were nodding as Sean displayed the trial data.

The forty-seven percent reduction in implant rejection was a massive victory.

"The clinical research division commissioned this specific device development," he told the crowd.

"This breakthrough exists entirely because of our clinical programme's institutional framework."

"When we look at the reduced rejection rates, we see the power of our clinical strategy."

I looked at the screen.

He clicked the presentation remote to show the next detailed slide.

"We consider this the hospital's clinical engineering breakthrough," he continued.

"It is our clinical research division's supreme development, and we are proud to introduce it today."

He did not name the biomedical device development unit.

He did not mention engineering log BPD-ENG-2021-007.

He did not say my name.

I looked up at the massive presentation screen.

The bright slide displayed the detailed three-axis articulation diagram.

I recognised the exact angle of the titanium shell.

It was the precise schematic I had drafted three years ago.

I folded my printed conference program in half.

I placed it inside my leather bag.

I stood up from my seat in the middle row.

I walked down the carpeted aisle and out of the auditorium.

The hallway outside was completely quiet.

The presentation slide credited the clinical research division.

The three-axis articulation diagram on the screen was the one I drew.

(Read more in the first comment below)

06/17/2026

The key-generation loop failed the third automated test run on my primary monitor.

The state variable reset completely before the cryptographic key could finish its active cycle.

The red error text flooded the terminal window.

I lean back in my heavy desk chair.

I reach into my left jacket pocket.

I pull out a loose Cherry MX Blue mechanical keyboard switch.

The small component features a clear plastic housing and a bright blue stem.

It belonged to the Q key on my custom-built mechanical board.

It stopped registering keystrokes during a critical design session back in 2021.

I press the plastic stem firmly against my thumbnail.

I feel the sharp tactile bump.

I hear the distinct, familiar click echoing in the quiet room.

I keep the broken switch with me at all times.

The physical feedback grounds my focus when a structural architecture feels fundamentally wrong.

I press it against my nail a second time.

I lean forward.

I look back at the dense lines of code on my screen.

I trace the state variable backward through the complex encryption loop.

I examine the syntax line by line.

I find the exact reset condition buried in a single string of code.

It has an incorrect operational scope.

I rewrite the parameter.

I clear the terminal window.

I initiate the fourth automated test suite.

The program compiles and runs the diagnostic.

The terminal flashes a solid green confirmation bar.

I log the final result into my project directory.

The AKS-1 key-generation loop version four is completely stable.

I slip the mechanical switch back into my jacket pocket.

I am a professional codebreaker and cryptanalyst.

I work for an independent cybersecurity consultancy.

My primary focus is developing complex cryptographic architectures.

I build systems that dynamically adjust key generation based on live network state variables.

This adaptive methodology makes brute-force server attacks computationally infeasible at an enterprise scale.

It requires attackers to recalculate their approach every millisecond.

I published the foundational mathematics for this specific architecture last year.

The technical paper is titled "Adaptive Key-State Encryption, J. Okafor."

It is permanently archived in the Journal of Applied Cryptography.

It was formally published in Volume 8, 2022.

Leo Crane is my partner of three years.

He is also the Co-Founder and CEO of AKS Security Ltd.

Two years ago, Leo stood directly behind my desk.

It was the exact night the AKS-1 algorithm first passed its full diagnostic test suite.

He watched the green confirmation bars cascade down the terminal window.

This was months before the academic paper was ever submitted for formal peer review.

He ran the final manual test protocol himself.

He sat very still in the glow of the monitor.

"This changes what's possible," he said.

He looked at the clean output logs on the screen.

"The market is flooded with static architectures that just wait to be broken by faster processing," he told me.

I looked at the terminal output.

"It needs formal peer review before it goes anywhere," I said.

He rested his hand on the back of my chair.

"I know it needs review," he replied.

"But right now, in this room, this changes everything about our trajectory."

He was absolutely right about what the algorithm represented.

Over the next three years, he presented AKS-1 to dozens of venture capital boards.

He showcased it to massive enterprise clients.

He aggressively pitched it as the proprietary flagship product of his startup.

He built a massive corporate valuation entirely on the back of my mathematical architecture.

Today is the official acquisition press conference for AKS Security Ltd.

A major defense contractor is acquiring the startup specifically for its encryption portfolio.

The final valuation sits at one hundred million dollars.

I sit at my home workstation.

I open the live video feed on my secondary monitor.

Two hundred press members and institutional investors fill the massive corporate auditorium.

The camera pans across the crowd of reporters.

Leo sits on the main stage wearing a dark tailored suit.

The defense contractor's Chief Technology Officer stands at the main podium.

He is preparing to deliver the technical rationale for the massive acquisition.

I open a secure email sent to me this morning.

It came directly from the startup's corporate legal team.

The email contains the final acquisition agreement's intellectual property schedules.

I open the dense PDF file.

I scroll through dozens of pages of corporate boilerplate.

I locate Schedule 4.

This specific section details the legal transfer of the adaptive encryption algorithm.

I read the legal schedule on my primary monitor.

It explicitly lists AKS-1 as an AKS Security Ltd. proprietary algorithm.

It states the intellectual property was developed entirely in-house by the startup team.

This contested clause legally bars me from using my own algorithm in my independent practice.

I am officially locked out of my own code by a corporate entity.

On the livestream, the CTO leans into the podium microphone.

"The core of this acquisition is AKS-1," the CTO announces to the crowded room.

"It is a breakthrough in adaptive encryption that changes the field."

The journalists in the front row are typing rapidly on their laptops.

"The algorithm was first published as Adaptive Key-State Encryption, J. Okafor, Journal of Applied Cryptography, 2022," the CTO says.

He names my technical paper directly into the microphone.

He says the exact words "first published."

He names my exact initial and surname to two hundred journalists on the live broadcast.

"We acquired the startup to bring this technology into our defense systems," he concludes.

I sit alone in my home office.

I listen to the camera shutters clicking over the audio feed.

I close the email client on my primary monitor.

I reach into my left jacket pocket.

I pull out the Cherry MX Blue switch.

I place the plastic switch flat on the wooden desk.

I do not look away from the two monitors.

I press the blue stem once against my thumbnail.

I feel the tactile bump.

I hear the distinct click.

The live press conference transcript clearly stated J. Okafor.

The permanent legal schedule stated AKS Security Ltd. proprietary.

(Read more in the first comment below)

06/17/2026

Three years ago, Felix Renard stood right at the edge of my wooden workbench.

He watched me test the raw escapement mechanism for our very first tourbillon prototype.

"Nobody in Geneva has done this in a production movement," he said.

"If you solve the constant-force problem, this will be the most significant tourbillon in independent watchmaking."

I picked up my precision tweezers.

I adjusted the balance spring.

I am a horologist in a luxury boutique workshop.

I engineer proprietary mechanical movements from raw schematics to final assembly.

I spend my days seated at a high magnification microscope, manipulating microscopic brass gears and fine steel pinions.

I mark my personal instruments with my initials in permanent marker on the shaft.

I do this because specialized tools get mixed across shared bench sessions, and I need to identify mine immediately.

The letters "T.M." sit just below the grip on my primary micro-screwdriver.

I dropped the instrument on the hard workshop floor four years ago.

The impact broke a tiny piece of the painted surface on the left side of the handle.

I kept it because the chipped handle fundamentally changed the grip point in my fingers.

I re-calibrated my torque feel entirely around that specific physical chip.

No other screwdriver in the workshop provides the exact same feedback to my hand.

I pick it up and align the 1.2mm blade with the barrel bridge screw.

I make exactly three rotations.

The chipped paint tells my palm exactly when the torque is perfectly set.

The movement resting on my bench is the TM-CF-01.

It took three years of concentrated development, countless failed brass prototypes, and hundreds of hours of mechanical drafting to reach this final stage.

There are two hundred and fourteen individual micro-components resting in the brass cleaning tray beside my microscope.

I use my tweezers to lift the delicate balance wheel from the tray.

I apply a microscopic drop of synthetic oil to the jewel bearing.

I place the barrel bridge over the gear train and secure the micro-screw.

I lean forward and check the constant-force spring engagement under my high-magnification loupe.

This specific mechanism regulates the energy flow to the escapement.

It ensures absolute precision regardless of the mainspring's tension over a seventy-two-hour power reserve.

I test the gear interaction with the tip of my tweezers.

I do not over-tighten the setting.

The thick technical specification file sits on the edge of the wooden bench.

It is a dense binder filled with schematics, stress tests, and mathematical proofs.

It reads: TM-CF-01, T. Müller, Development Record 2021–2024.

This document is permanently held in the boutique's locked engineering archive.

It serves as the technical foundation for the movement's official nomination for the prestigious Grand Prix d'Horlogerie de Genève.

Felix is my partner of seven years, and he is the owner and creative director of the luxury watch boutique.

His office is lined with leather chairs, presentation screens, and polished mahogany tables.

He operates far away from the oil and brass dust of the workshop.

He handles the high-level client presentations, the international press releases, and the overarching brand narrative.

For seven years, he has presented my horological engineering work as the boutique's primary technical signature.

He uses the complex movements I design to secure industry prestige and command astronomical retail prices from international clients.

My name has never appeared in any public document or press release.

Two days ago, I stood at the edge of the boutique's main showroom for the limited-edition watch launch event.

The large retail space smelled like expensive catering, dry champagne, and polished glass display cases.

Eighty high-end collectors, three international watch journalists, and the official Grand Prix nomination committee observer stood around the room.

The new watches rested inside illuminated glass vitrines on black velvet cushions.

Felix stood at the front of the room in a tailored dark suit.

He held a microphone and presented the new limited-edition tourbillon to the gathered crowd.

"This watch represents my vision for a new standard in tourbillon mechanics," he said to the room.

"We have pushed the boundaries of independent horology."

He gestured toward my position near the back wall.

"I want to acknowledge Thea, our precision assembly technician who realised the movement's final form."

He smiled warmly at the front row of collectors.

The crowd politely applauded the assembly technician.

I stood exactly three metres away from the nearest display table.

I looked past the wealthy collectors and focused on the watch in the heavy glass case.

It was the TM-CF-01.

It was my two hundred and fourteen components, my constant-force spring, my three years of intense engineering.

I walked slowly toward the illuminated display table.

I looked down at the thick black display card resting right beside the watch case.

The text was printed in sharp silver typography.

It said: "TM-CF-01 Tourbillon."

Below the title, it said: "Designed and Created by Felix Renard."

A collector stepped up beside me.

He picked up the heavy watch to examine the complex movement through the clear sapphire case back.

He was looking directly at my movement.

I put my hand into my apron pocket.

The micro-screwdriver was not there.

I had left it on my workshop bench.

I turned around.

I walked out of the crowded showroom.

(Read more in the first comment below)

06/16/2026

I opened the velvet roll on the conservation bench.

I smoothed the dark fabric flat under the harsh fluorescent laboratory lights.

The precision steel tweezers sat exactly where they always did, right in the second slot from the left.

I am an antique textile restorer for a private museum conservation department.

I specialize in the structural recovery of historical fibers that most major institutions consider completely beyond saving.

The sixteenth-century Flemish tapestry took up the entirety of the central work table in my lab.

It was a masterwork valued at 4.2 million euros.

It depicted a faded hunting scene woven in delicate silk and wool.

For decades, the institution had considered it entirely unrestorable due to a severe, hardened corrosion layer that had bonded to the fragile base threads.

Any standard cleaning attempt would have shattered the ancient fibers into dust.

I had spent eight months developing a custom three-stage chemical restoration process specifically to save this single piece.

The protocol required a localized enzyme wash.

It required a highly specific pH-stabilized consolidant.

It required a reversible wax consolidation.

I picked up my eighteen-centimeter tweezers.

They were made of heavy stainless steel.

They tapered down to an ultra-fine micro-tip designed for individual thread manipulation.

On the inside of the grip handle, a small stamped font was permanently engraved into the metal.

It read ST-14.

It was my instrument number.

It was my personal stamp.

It was my most trusted tool.

I had started numbering my instruments years ago after a loaner tool was confused with my personal kit.

The habit had stuck ever since.

I prepared the localized enzyme wash in a sterile glass beaker at the edge of the bench.

The chemistry was entirely unforgiving.

If the pH balance was off by a fraction, the ancient dye would bleed.

The enzyme had to pe*****te perfectly under the corrosion layer without disturbing the surrounding healthy fibers.

I leaned over the magnification glass.

I held my breath.

I gripped a single delicate weft thread with the micro-tip of the tweezers.

I applied the pH-stabilized consolidant to a microscopic five-millimeter section of the central motif.

The clear liquid absorbed slowly into the centuries-old thread.

I watched the structural integrity hold firm under the intense magnification.

The fiber strengthened instead of snapping.

It took forty-five minutes of absolute silence to stabilize that single five-millimeter section of the tapestry.

I exhaled.

I set the ST-14 tweezers back into their dedicated slot in the velvet roll.

I pulled the conservation lab’s heavy accession record and process log toward the center of my desk.

The thick binder’s cover read Treatment Log TL-2024-0077.

I uncapped my archival pen.

I carefully recorded the details of the afternoon's session.

I wrote my initials and my exact instrument reference at the very top of the new entry.

S.N. / Inst. ref. ST-14.

I had executed this exact ritual for forty-seven consecutive treatment entries over the last eight gruelling months.

Every localized wash was documented in these pages.

Every enzyme variation was noted.

Every consolidant application was documented.

Every reversible wax consolidation was meticulously recorded in ink.

Every single entry bore my initials and my specific tool number.

The museum's main gallery always smelled like expensive floor polish and donor money.

Victor Marsh stood near the illuminated display cases in a tailored navy suit.

He smiled at a passing board member.

He was the museum's Head of Conservation.

He was the charismatic architect of the department's external funding.

He was my partner of six years.

Two months ago, he had walked into my lab while I was logging a treatment session.

"The European Textile Conservation Foundation requires institutional leadership for this fellowship," he said, looking at the paperwork in his hand.

"They evaluate the museum's overarching capability, not just individual bench work," he continued.

I kept my eyes on the delicate weft thread.

"I am framing the restoration as a departmental initiative," he said smoothly.

"It positions our entire program perfectly for the next major funding cycle," he added.

I set the beaker down.

He smiled, a man completely comfortable with his own logic.

"The application abstract focuses on my role as Head of Conservation," he told me.

"It is the only way the committee will approve the grant," he concluded.

I picked up the ST-14 tweezers.

He had meant it.

He had submitted the massive fellowship application that same night.

He had not informed me of the specific language he used in the official documentation.

I had simply assumed it was just another routine administrative funding round that did not require my input.

I was wrong.

The heavy black phone on the conservation lab wall rang loudly at two in the afternoon.

I set the ST-14 tweezers down gently on the sterile mat.

I walked over and answered it.

"This is Dr. Margit Wolff," the crisp voice said.

"I am a verification officer with the European Textile Conservation Foundation," she stated.

I wiped a small spot of dried consolidant from the thumb of my nitrile glove.

"How can I help you, Dr. Wolff?" I asked.

"We are currently reviewing the fellowship application," she said, her tone professional and steady.

"The process log attached to the application names S. Nouri on all treatment entries," she informed me.

I stopped wiping the glove.

I stared at the wall.

"Can you confirm your role in the restoration described in the application?" she asked.

"I developed and led the restoration treatment," I said to the empty room.

"Thank you," Dr. Wolff replied immediately.

"We will be in contact shortly," she said.

The line clicked dead.

I hung the receiver back on the wall hook.

I walked slowly back to the central table where the priceless Flemish tapestry lay pinned under the bright lights.

I sat down.

I opened the conservation system on my lab computer.

I pulled up the digital copy of Treatment Log TL-2024-0077.

I scrolled past the title page.

I looked at the first entry.

Forty-seven entries.

Forty-seven times: S.N. / ST-14.

Then I searched the department's shared network for the fellowship application abstract Victor had submitted to the committee.

I clicked through the outbound funding folder.

I found the PDF file buried at the bottom of the directory.

I opened it on my screen.

I read the executive summary.

The document formally named Victor Marsh as the sole project lead.

I closed the application file.

I closed the process log.

I picked up the precision steel tweezers from the mat.

I placed them securely inside the second slot of the velvet roll.

I rolled the dark fabric closed.

The application abstract described a museum-led conservation initiative directed by the Head of Conservation.

The attached supporting log entries said S.N.

(Read more in the first comment below)

06/16/2026

The topographic map roll sat on my desk with the annotated side facing inward.

The reference code strip faced out.

It read: CSM-2024-0029 / PEAT-NORTH.

I am a climate scientist specializing in land-use and carbon sequestration modelling.

For the past three years, I have built a spatially explicit carbon sequestration model for the national peatland network.

The model integrates soil organic carbon, aboveground biomass, and complex land-use history at a precise two-hundred-and-fifty-meter resolution.

I spend most of my weeks translating raw soil organic carbon depth measurements into actionable data arrays.

The physical maps anchor the digital models.

I work with thick field-weight paper and black gel pens.

I always roll my topographic maps with the working layer hidden inside.

The annotations are the last thing I want to see when I open a new section.

I want the raw geography to speak first.

It was early Tuesday afternoon.

The spatial analysis laboratory was quiet except for the hum of the server racks.

I was entering the final land-use history layer into the main system.

I needed to log the 1987 drainage events across the northern peat grid before I could finalize the international submission.

I reached across the desk and unrolled the national peatland network sheet.

I flattened the heavy paper edges against the wooden table and weighed the corners down with my brass calipers.

The soil core locations were marked in precise black gel pen dots.

The boundary corrections were drawn in sharp lines across the topographic grid.

I traced the geographic coordinates with my finger and typed the historical drainage data into the model framework.

Every gel pen mark represented days of fieldwork and verification in the wetlands.

Every boundary line was a calculation I had made using deep soil sampling and organic carbon depth measurements.

I checked the input parameters against my physical field notebook one last time.

I pressed the ex*****on key.

I ran the simulation sequence.

The system took several minutes to process the millions of spatial data points.

The screen finally refreshed and displayed the final carbon sequestration output.

The calculated number was 4.2 million tonnes of carbon dioxide equivalent across the network for the 2024 baseline.

I picked up my pen.

I wrote the exact figure into the formal submission document.

Model reference CSM-2024-0029 was officially ready for the IPCC working group.

I opened the secure portal and uploaded the spatial files.

I registered the data in the official submission record.

The system generated a confirmation receipt and displayed the developer name as C. Rossi.

The documentation was locked into the international scientific registry under my credentials.

Lars Svensson walked past the laboratory door holding a stack of briefing folders.

He is my partner of six years and a Senior Policy Advisor at the National Environment Agency.

He was preparing for the upcoming ministerial committee meetings.

Five years ago, he stood at this exact desk when I showed him the first preliminary peatland model output.

I only had sixty soil core points for the northern network back then.

He leaned over my shoulder and traced the limited grid lines on the monitor.

"If you can get this to national coverage, it'll be the best carbon accounting dataset the Agency has ever had," he said.

I nodded.

He arranged the initial fieldwork budget through his policy department.

I spent the next three years in the mud collecting two hundred and forty more soil cores to achieve full national coverage.

I built the exact analytical dataset he asked for.

The government environment policy brief arrived in my inbox at two o'clock.

The email was sent from the Director's office.

The subject line read: Finalised Ministerial Briefing Document.

It was not a draft sent for review.

It was a completed document ready for the ministerial committee.

The distribution list at the top of the email included twelve senior ministry officials and four international observers.

I moved my cursor over the attachment and clicked it open to review the final text.

I scrolled past the executive summary and the strategic policy recommendations.

I navigated directly to the methodology section to check the formal citation for my carbon sequestration model.

I read the attribution language twice.

It was printed in standard Arial font under the primary data source heading.

It read: "Analysis conducted by the Agency's policy team."

My name was nowhere in the twenty-page document.

I had not been consulted on the text.

I had not been asked about the phrasing.

I checked the email distribution list again.

Twelve ministry officials had already received it.

I opened a second window on my monitor.

I pulled up my IPCC data submission record from the secure portal.

The screen showed the formal model reference number.

CSM-2024-0029.

The developer line was absolute.

C. Rossi.

I dragged the IPCC record next to the government policy brief.

One document credited my work to the international scientific community.

The other erased my identity entirely from the official ministerial record.

I closed the IPCC submission window.

I closed the government policy brief.

I pushed my chair back from the desk.

I picked up the topographic map roll.

I rolled the heavy paper tightly with the annotated side facing inward.

I set it on the map stand with the code strip facing out.

I did not reply to the distribution email.

*(Read more in the first comment below)*

Address

1100 S Broadway
Los Angeles, CA
90015

Telephone

+12138061023

Website

Alerts

Be the first to know and let us send you an email when Marilyn P. Perkins posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Shortcuts

Share

Category