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.
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.
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.
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.