2,928 karma · joined April 12, 2019
Yes. I think an LLM can be useful for trivial or functional tasks, but for expressing complex positions, it's worse than useless. It's absolutely valid to dismiss LLM-generated prose, and people who who think they're doing 'assisted authorship' tend to be mistaken.
I'm not saying you are incapable of thought; I'm saying that you've abdicated that by transmitting through an LLM.
1. I do disagree with your position in both the prompt and the output; I don't think you're correct. That doesn't mean I don't think you're worth talking to.
2. I do think the output was thoughtless; there is thought evident in the prompt, but then you passed it through a blandifying filter that took it out. You made your contribution less valuable and less valid, removing intention. That's thoughtless.
You do not need a filter; it does not make your writing better, it makes it more pallid.
I don't agree that it's ableism to believe that you are far more worth talking to than a machine regurgitating attenuated averages.
You didn't put any meaningful thought into it.
The purpose of writing is to communicate. The person communicating is an important part of the message.
Consider the sentence "I'm waiting for you at home." It really matters if it's said by your loving wife or an evil clown. You can extrapolate from this.
Why would you think it would?
Software engineers have adopted this more than any other profession. The breathless articles about it being the end of knowledge workers, a superior being, even god: all of these are coming from the tech world.
It simply isn't true that tech people are somehow the smart ones above the masses; it's a comforting old paradigm, but it doesn't add up. It's developers who are the most amazed, the least critical.
It's a word that's thrown around a lot (particularly in tech) that rarely has much to back it up. Often, it seems to be used for 'confident young man', or even 'grifter', and then when the idol falls, the same people quietly focus on lionising someone new.
If the worry is that the cop you hand your phone to will take more access than you want, then attempting to limit that access is probably not going to work out the way you want.
A more effective solution would be better legal protections.
Some people thought this. Some people didn't. Some people thought it was a step backwards. We don't have a solid ground-truth way of estimating this.
You'll forgive me if I remain unconvinced.
I don't think this is attributable to the 'learn to code' push; I know many fine engineers who came through boot camps, and many, many poor ones who came in the 'official' way.
The problem is that we trained too many people, many of them without the aptitude, not how we trained them.
All you need to have Fable-level AI is to announce it, and have enough fans shift from insisting that model Y is the best now, way better than model X.
Accepting something without evidence and only challenging things that disagree with your evidence-less beliefs is the exact opposite of even-handed.
But with two competing claims, and no easy way to check ground truth, you absolutely ask for citations from both sides. There's nothing rational about uncritically accepting the narrative you heard first.
It's not. I have no idea how you got there.
The right thing is to seek evidence for both perspectives. This is ironically not rocket science. Don't accept any viewpoint just on say-so, but especially don't pretend to sneering objectivity when you do so.
Demanding evidence from one party while accepting the word of the other is not even-handed.
I think the knowledge being absorbed is 'how to use AI to make apps', not necessarily anything about the code itself. I've seen lots of people who are very effective with AI suddenly poleaxed in interviews without it. Going from 'able to explain exactly what needs to happen' to 'staring at a blank page with no ideas'.
The only way I've found to make juniors develop that instinct is to make them do it until it comes naturally--to continually demand they verify their assumptions, test out theories while debugging. If you don't practice being comfortable with the unfamiliar, you lose the knack.
It's fine, of course, to lose the knack to AI, as long as you'll never need to solve a problem the AI can't (or can't access). I don't think that's a good assumption for everyone to make.