I’m now convinced that most holodeck malfunctions are the result of end users, who don’t know what they’re doing, using AI to generate poorly-written software they’re ill-equipped to debug or even really understand.

43 points
*

All the holodeck shows is that even in the 24th century people still don’t know how to properly implement least privilege access controls.

permalink
report
reply
20 points

Or bounds checking. Or sandboxing.

permalink
report
parent
reply
22 points

Or post mortem. Seriously? A second and third identical failure? Implement some guardrails Starfleet!

No joke I would have loved an episode where Rutherford and Tendi find all the trash code in the holodeck and replace it with code following a proper CI/CD pipeline.

permalink
report
parent
reply
7 points

“I still support the railing systeeeeeeeem!”

permalink
report
parent
reply
14 points

Or just locking the door.

permalink
report
parent
reply
9 points

Or manual circuit breakers

permalink
report
parent
reply
2 points

And I’m shocked that there’s no guardrails to prevent users from making RP fanfic.

permalink
report
parent
reply
33 points

Speak for yourself. The D’s holodeck was always fucking up and sending historical villains running amok and whatnot, but Quark’s holosuites always worked fine.

permalink
report
reply
27 points

Yea, cause the Binars fucked with in season 1 specifically to give it the ability to make sapient AIs. Apparently nobody ever did a factory reset after that.

permalink
report
parent
reply
16 points
*

Nah, that same upgrade got rolled out industry-wide. Remember Vic Fontaine?

permalink
report
parent
reply
5 points

My headcanon is that Dr. Zimmerman received the Moriarty program from Barclay, and discovered from it how to make sentient holograms, which is why holograms started getting sentient more regularly and by design.

permalink
report
parent
reply
2 points
*

Not at all. Vic was running on Quark’s holosuites. They were not owned, serviced or built by the Federation.

permalink
report
parent
reply
17 points

permalink
report
parent
reply
3 points
*

Enterprise didn’t have Rom onboard to fix them, thats why.

permalink
report
parent
reply
24 points

I mean 2 of the smartest people on the Enterprise D accidentally created an artificial lifeform and had no safeguards to prevent it from happening.

permalink
report
reply
13 points
*

I guess ‘accidental, megalomaniacal sapience’ is technically a holodeck malfunction, lol. I wasn’t even thinking of that incident.

permalink
report
parent
reply
5 points

Really just one person- Geordie- through an accidental misphrasing of a request to the computer.

I would have never used that computer again. Or at least given it a complete overhaul. You shouldn’t be allowed to do the sort of thing you’d request of Dall-E in order for the computer to create intelligent life.

permalink
report
parent
reply
4 points

Yeah, they could stand to at least add a, “This request will result in the creation a sentient being, are you sure you wish to proceed?” warning.

permalink
report
parent
reply
5 points

Really, a lot of Star Trek problems could be averted with a “are you sure you want to do this?” before someone does something with the computer or the holodeck. Starfleet apparently never learns. That’s why in Prodigy-

spoiler

Janeway goes back to the Delta Quadrent in a different ship of a different but similar-looking class renamed Voyager.

permalink
report
parent
reply
2 points

Frankly I would posit that present-day LLMs demonstrate exactly why Moriarty wasn’t even necessarily sapient.

permalink
report
parent
reply
20 points

We should call these “Sonic Shower Thoughts”

permalink
report
reply
13 points
*

Yes, we should, and I just updated the title.

permalink
report
parent
reply
17 points

I haven’t been a professional developer in a long time, but I feel like this needs to be said; No, the end user is never the problem. There is no such thing as a use case that is not the end user, because as soon as you use it you become the end user. The entire point is to make the product usable. No, the end user breaking things is not some kind of moment to laugh at them - you should be embarrassed.

That being said, I lol’d.

permalink
report
reply
8 points
*

I guess this is a bit of a crossover situation. The end-user is the developer in this scenario. I guess you could also say they’re the end-user of the AI software as well, but that’s not software I’m responsible for (and have advocated against)

The IRL back story of the post is my org is experimenting with letting end-users use AI-assisted, no-code platforms to develop line-of-business software. Sounds good on paper, but they don’t understand anything they create, and when it doesn’t work or otherwise produces unexpected results (which is often), it suddenly becomes my problem to debug the unmaintainable crap the “AI” spits out or click around 10,000 times in the Playskool “development” GUI the platform uses to find the flaw in their Rube Goldbergian-logic.

It’s basically like I’m Geordi or O’Brien and am getting called all day and night to debug people’s fanfiction holonovels. lol.

Which is super annoying because had they just asked or put in a request, I or someone on my team could have developed something properly that could be easily maintained, version-controlled, extended, and such.

permalink
report
parent
reply

TenForward: Where Every Vulcan Knows Your Name

!tenforward@lemmy.world

Create post

/c/TenFoward: Your home-away-from-home for all things Star Trek!

Re-route power to the shields, emit a tachyon pulse through the deflector, and post all the nonsense you want. Within reason of course.

~ 1. No bigotry. This is a Star Trek community. Hating someone off of their race, culture, creed, sexuality, or identity is not remotely acceptable. Mistakes can happen but do your best to respect others.

~ 2. Keep it civil. Disagreements will happen both on lore and preferences. That’s okay! Just don’t let it make you forget that the person you are talking to is also a person.

~ 3. Use spoiler tags. This applies to any episodes that have dropped within 3 months prior of your posting. After that it’s free game.

~ 4. Keep it Trek related. This one is kind of a gimme but keep as on topic as possible.

~ 5. Keep posts to a limit. We all love Star Trek stuff but 3-4 posts in an hour is plenty enough.

~ 6. Try to not repost. Mistakes happen, we get it! But try to not repost anything from within the past 1-2 months.

~ 7. No General AI Art. Posts of simple AI art do not ‘inspire jamaharon’ and fuck over our artist friends.

Fun will now commence.


Sister Communities:

!startrek@lemmy.world

!memes@lemmy.world

!tumblr@lemmy.world

!lemmyshitpost@lemmy.world

Want your community to be added to the sidebar? Just ask one of our mods!


Honorary Badbitch:

@jawa21@startrek.website for realizing that the line used to be “want to be added to the sidebar?” and capitalized on it. Congratulations and welcome to the sidebar. Stamets is both ashamed and proud.


Creator Resources:

Looking for a Star Trek screencap? (TrekCore)

Looking for the right Star Trek typeface/font for your meme? (Thank you @kellyaster for putting this together!)


Community stats

  • 5.8K

    Monthly active users

  • 2.4K

    Posts

  • 35K

    Comments