fionaNov 26

I find it disillusioning to see the casual use of "AI" slowly creeping into our hacker circles. Most of the discussions about AI focus on the quality of its output. I think we're not doing a good job communicating its more fundamental dangers.

In this blog post I write about how tools shape who we are and why the resource intensiveness of AI is ingrained in its purpose. About the devaluation of skills, and power cycles.

Let me know what you think.

https://fokus.cool/2025/11/25/i-dont-care-how-well-your-ai-works.html

I don't care how well your "AI" works - fiona fokus

Show threadGabeMoralesVRNov 26
@fionafokus When AI was first all the buzz, I downloaded gpt4all, and fed it a *ton* of Sega Dreamcast hacking notes I and others had compiled. Figured I could use it like a quick reference. First day, I tried to ask it some things, and was impressed how it had answers. Then I tried implementing the answers, and quickly realized it was constantly full of shit. Even when trained entirely locally on hyper specific documents, it'll lie and give me crazy bullshit answers. It's useless for this stuff
Show threadGabeMoralesVR
@fionafokus In order to actually effectively use AI like this, you have to know the subject to be able to constantly check its work, which defeats the purpose of using a cheat tool to get around knowing the subject. It's like a dunning-kruger machine, how much you trust it reveals how little you know about the subject.
Nov 26 at 12:43amWeb
Show threadGabeMoralesVRNov 26
@fionafokus I see people be like "just use it for boiler plate!" except I work in embedded systems that are performance bottlenecked and need to be optimal. This generated boilerplate code has no regard for cache, no regard for smart register usage, etc. It's like the world's most slightly-below-average programmer doing the work for you.
Show threadAutoerotic DefenestrationNov 27
@GabeMoralesVR @fionafokus also, there are a lot of tools that reliably produce boilerplate without AI.