jwoq9118
Joined 2 years ago
Joined 2 years ago
All I can say is I know because I know. There's been some "synergizing" among the corporation about the CLI team running off to do their own thing and adding features to the CLI that amount to trying to force a Terminal to act like a GUI.
I hate that em dashes have been killed by AI as well. Hundreds of years ago Charles Dickens was using them in his novels and today someone will read his books and in ignorance actually think AI wrote it.
The hype is so large with the CLI coding tools I got FOMO, but as you were saying in that thread, I see no tangible improvement to the value I get out of AI coding tools by using the CLI alone. I use the CLI in VS Code, and I use the chat panel, and the only thing that seems to actually make a difference is the "context engineering" stuff of custom instructions, agent skills, prompt files, hooks, custom agents, all that stuff, which works no matter which interface you use to kick off your AI coding instructions.
Would be curious to hear your thoughts on the topic all these months later.
https://www.businessinsider.com/anthropic-claude-code-founde...
I see people get a morning coffee, get lunch and a drink, and then maybe something on their way out. It’s not a problem.
Reading through those comments, one stood out to me.
> AFAIK the idea was that SQL is so close to plain English that any accountant could simply use it to generate reports or enter data. It's really an old fallacy that using plain language would make complexity go away. > > beew001
Was responding to a thread about how SQL was meant to be "low code" if not "no code", and even COBOL before it.
Now in 2026 with LLMs I'm finding a lot of what's said in that comment section is still true. Would love if some commenters from that original thread popped back in here.