| ▲ | whatever1 8 hours ago |
| Whoever claims to have skill in AI is very shortsighted. Whatever skill you thought you had six months ago can now be achieved with a simple six-word prompt in a standard workspace. I literally just ask a frontier model : "Pull the latest log and root cause the issue.". That's it, 10' later it comes back with a correct answer. Sometimes I might have to prompt a second time to steer. No skills, agent interconnections, graphs, vector search or whatever else. The progress is very scary. |
|
| ▲ | Animats 8 hours ago | parent | next [-] |
| > Whoever claims to have skill in AI is very shortsighted. Whatever skill you thought you had six months ago can now be achieved with a simple six-word prompt in a standard workspace. Apparently. Remember "prompt engineering?" That was the next big job for about 15 minutes. It takes a lot of tokens to run a multi-agent system, though. AI may hit economic limits. Progress was achieved on hard mathematical problems at a high token cost. More than the operating budgets of some college math departments. |
| |
| ▲ | margalabargala 7 hours ago | parent | next [-] | | > at a high token cost. More than the operating budgets of some college math departments. Is that in API cost or in subscription cost or in actual cost to the LLM owner? | |
| ▲ | somewhereoutth 7 hours ago | parent | prev | next [-] | | Wouldn't it be ironic if, after all this, it was discovered that the most economical way of producing some fundamental 'unit of intelligence' was to feed/clothe/entertain a human? | | | |
| ▲ | rubikscube09 an hour ago | parent | prev [-] | | eh, hardware will get more efficient. moore's law and whatnot. |
|
|
| ▲ | vanuatu 8 hours ago | parent | prev | next [-] |
| the bulk of the skill lies in shoring up the fundamental limitations of llms they cannot be held accountable - therefore, you need the skill and expertise to verify outputs, or set up a verifier they have a limit to their context window - therefore, you need the skill of knowing what context is useful and exposing that they cost money and time to run - therefore, you need the skill of learning what parts can be handed off to code, when you can use a cheaper model, when you tradeoff accuracy vs latency they are nondeterministic - therefore, you need the skill to set up evals, guardrails, knowing when to reach for the llm vs. code depending on the problem they are not omniscient - therefore, you need the skill of setting up the processes and infra to supply legible context to the llms etc etc |
| |
| ▲ | leecommamichael 7 hours ago | parent [-] | | We still have yet to find what is possible without a career's worth of experience doing it all by-hand. |
|
|
| ▲ | onlyrealcuzzo 8 hours ago | parent | prev | next [-] |
| It seems to me as though you're describing a skill... What would happen if you just screamed: "SAVE ME! EVERYTHING IS BROKEN! I'M STUPID MONKEY!" I mean, sure, this might not seem like a lot of skill to you, but you at least have a clue what you are doing, and not everyone does. |
| |
| ▲ | 0c3ca83 8 hours ago | parent | next [-] | | Is your bar for skill "name the symptom you observed"? | | |
| ▲ | ghosty141 8 hours ago | parent | next [-] | | Most sales jobs would be unnecessary if people would be good at communicating their problems. | |
| ▲ | rcxdude 8 hours ago | parent | prev [-] | | I mean, if a large fraction of the population seem to lack it... It also, in my experience, can be taught. |
| |
| ▲ | rootusrootus 8 hours ago | parent | prev | next [-] | | Okay, admittedly this is not necessarily a great test, but I decided to try it anyway. I loaded up Claude Code and then gave it that prompt. You're not stupid, and we'll figure it out. I'm taking a read-only look at the system now to see what's actually broken.
Then it ran some commands, and came back with: The machine itself looks healthy, so whatever broke is more specific than "everything" and I need you to point me at it.
It listed out some stats based on top and some investigating the filesystem numbers, running processes, etc, and then said: What were you doing when it went wrong: which command, app or URL, and what error did you see? If it's the p3 containers, tell me how you normally start them and I'll dig in from there.
I'm not feeling super creative this afternoon, so I just said "Everything is slow!" It politely told me that it cannot see anything with the CPU, memory, or disk that suggests it is slow, and that I should check out the host. It knows it is in a VM on MacOS. Told me where to go to look for more info.Now picture it running in Cowork instead of CC, and it would probably tell non-technical users what the real problem is. Or at least give them something to hand to IT. What a world. | | | |
| ▲ | krackers 8 hours ago | parent | prev [-] | | "Theory of mind" is all you need... |
|
|
| ▲ | xinweihe 2 hours ago | parent | prev [-] |
| [flagged] |
