Markets try to put things in perspective to sell more. Remember razors used to be for men only? But hte brilliant marketer (forgot the name) made it so that trimming makes women more feminine? Now razor sales doubled?
Anyways, same thing here. Those who want to sell AIs want to make it as non-tool but know-it-all do-it-all for you. Those who wants to use it view it as a tool.
Just frame it the way you like to see how you should use/view AIs.
The meta at this point seems to be mostly around "knowing what to ask for". Eg: I suck at prompting for specific design tweaks, because I don't have the design vocabulary to be specific and articulate what I want. It's a lot of trial and error. I hear people who are developing full scale applications without a tech background run into the issue writ large. For now, I have an advantage over these people when building applications. But perhaps that's just one round of RL away from being obsolete too. Supposedly the model will eventually have such good taste in design/architecture/whatever there will be little point in asking for tweaks.
The only thing that seems relatively future-proof is just being able to communicate clearly what you're trying to do. Not how to do it, or even what success looks like. Perhaps an element of it is even as basic as being honest with yourself.
Personally I've been very hesitant to deep-dive into putting together the perfect AI-workflow, I've been sticking to just using the conversational/chat modality for pretty much everything, usually that gets me as far as I need. It's just really hard to justify spending time on it when it all potentially gets turned upside down next month again.
And that skill is? Any concrete verifiable examples? That can be replicated, repeated by others or adopted by others?
> A compiler performs substantial work without the programmer continuously directing each operation.
Yes, and the compiler produces the same output for the same input all the time. And when it doesn't, it's a bug or a specified behaviour [1]
> Picking up a saw does not guarantee a straight cut. Holding a chisel does not make you a sculptor.
Yes, but you can learn the actual techniques that let you make a straight cut 100% of the time. And make you a sculptor.
---
The rest of the small article doesn't even begin to approach the premise of the title.
[1] Yes, I know it's not strictly true. But compilers are 100% predictable compared to LLMs.
no you can't? not by hand? not without a jig?
It is easy to argue otherwise, but to request a response in the form of a web app / embedded widget is at least some kind of AI proficiency that mirrors past experience having used a tool.
...AI codes an app...
> I don't like it. Make it like this.
...AI codes an app...
> I don't like it. See this app? Make it like it.
...AI codes an app...
> I don't like it. Hmm. Draw me an elephant.
...AI draws an elephant...
> I don't like it. This AI is stupid.
I miss the tools I used in the past (gcc, linux, sqlite,…)
https://github.com/openai/codex
https://github.com/MoonshotAI/kimi-code
https://github.com/mistralai/mistral-vibe
The current slew of excellent LLMs will probably cause a decades long dip in human cognitive ability.
If social media on smartphones had an impact of ability of students to concentrate, LLM AI will likely have a much greater negative impact on education.
There are trillions of dollars of investment pushing for humans to trust whatever an LLM says, and very little money behind encouraging people to tackle hard problems themselves and train themselves to think.
I have to say honestly, that AI looks like an apocalypse for human thinking [ Im glad Tao is warning people, I just dont think many people will listen ]
I don't know if I would call resisting this a skill, but it does take persistent intention and willingness.
> Stop using the lazy answer box, it will make you lazy.
And it minimizes the fact that these things are only getting smarter. Having an entity much smarter than you--could that entity seriously be considered your "tool"? Just your tool? Or are the people on the "just a tool" side of this debate not taking that possibility seriously?
Regardless of whether it is 'conscious' or not, Roman Yampolski makes the point that AI may or may not have human-kinds best interests at heart [ hell, even humans aren't aligned ]
Can we control or trust a counter-party that has intelligence at a level near or exceeding the smartest humans in all domains ?
I dont even think we can even have a safe sandbox in which to run an AI .. and frontier model training labs are certainly not air-gapped.
But in fact, as models get more powerful, the ceiling of what can be accomplished with them is raised, and their capacity as orchestration directors grows as well.
The market is shrinking, the pressure to review code is so high, I'm kinda relieved to not be at the $last_place anymore, but looking on LinkedIn or calling around my network... there isn't a lot out there.
The few AI companies have slurped up so much of human textual and artistic creation without attribution. They have taken enormous amounts of money from the public directly or indirectly and funneled it upwards to a few dangerous individuals.
When you say AI, learn to say "AI companies".
Professional photographers are different to everyday phone-photo takers because they have the experience built up over so many years in that sector, same as AI SWE, where the humans in the loop need experience to master AI SWE.
Interesting read on this: https://en.wikipedia.org/wiki/The_Work_of_Art_in_the_Age_of_...
I am pretty sure my wife could vibe code website or whatever at this point, or if not she will be able to in 6 months.
Rich's definition of "tool" is something like Ivan Illich's "Tools for Conviviality." Convivial tools can be used with minimal loss of agency, within a healthy politically-defined society. Huahai's definition is more akin to McLuhan's idea of "media." This category covers pretty much every technical or technological system, and its use is necessarily systematic and risks the instrumentalization of the user himself.
How I wish I could divulge details of what we’ve built, nay, shipped in the last 6 months - it would sound completely unbelievable to this audience and come with a host of accusations
But it’s true - the tide hasn’t risen all ships the same though. Some engineers have become absolute monsters - things that used to take a month get done in days. Features that used to be prioritized on the order of weeks are done way faster.
Some engineers though? Even high performance ones have gone productive to bottom 25% by some measures
Why? Because it is a skill and it doesn’t come naturally to everyone
So many may sayers everywhere talking about more code less software, mistakes by ai with disastrous consequences- yet I’ve seen some remarkable stuff with my own two eyes. It’s a crazy time to be in this business, it’s awesome to be wowed everyday by what someone was able to do
We came full circle on the problem that also exists with Google Search, and why so many people don't get good results out of it.
> For now, I have an advantage over these people when building applications. But perhaps that's just one round of RL away from being obsolete too.
I don't have a crystal ball, but my eggs are in the basket of "It isn't, and it won't be"
> The only thing that seems relatively future-proof is just being able to communicate clearly what you're trying to do
This somehow contradicts the previous statement. The advantage you have is, because of domain knowledge expertise, you're able to articulate what you want. It's not that you knowing what LazyLoading is that you now can describe it better, you can immediately tell that when your Frontend stalls for 5 seconds after hitting the "Load" button, perhaps it eagerly loads and blocks.
Fair point on the contradiction. I don’t have the answers either.
I may be misunderstanding your earlier statement then. The moat here is the knowledge, or how would the next iteration of RL solve that?
> it’s just that it can and should be faster.
Not sure if "Make it faster" works, it sounds like "Make no mistakes" 2.0
it's tons of small things like choosing the right effort level for a task. or knowing when to ask for subagents. oh, you can have two threads working at the same time and communicating with each other? you can do /side to parallel path and fold that back into the main thread?
which of these things happens automatically, and which do you need to ask for? and does any of this still work the way it did a few months ago?
the list goes on forever. many users of AI are only just now getting comfortable with skills (and probably still writing bad skills unfortunately hah).
A lot of the specific things you learned may have become obsolete. But there's still a gap between what these tools can do and what most people know how to get them to do.
Keeping up with that is a skill too but perhaps not forever.
Between biology advances remediating disabilities, customized outcome-driven education, potential advances in drugs that regulate executive function/memory/etc., improvements in nutrition, improvements in access, reductions in stress, I think we'll see people flourish.
And that's completely ignoring the more out there biological/computer merger style Sci-Fi outcomes, which I believe have a non-zero chance of occurring.
I'm 35 and have worked in ML generally for a decade and NLP for six years. Any other questions about my bonafides?
ChrisArchitect•38m ago
'AI' Is Not a Tool by Rich Hickey
https://news.ycombinator.com/item?id=50060269