I use AI a lot now. I find itβs best used when you can essentially interrogate it a bit against your own intelligence and use it for data collection, mathematical modeling, or coding tasks that you might could have actually done yourself but often wouldnβt have because the time constraints would have been immense.
An 11 year old wouldnβt catch on to that, but in their terms if they were going to use ChatGPT to write a paper for school, you have to be smart enough to not just put βwrite a 500 word essay on why white people are badβ but instead need to think to follow up going back and forth with it, have it add a spelling or grammatical error somewhere, make sure it looks like an 11yo wrote it and not a college student, etc. Beyond shaping output, if you ask me, in a lot of cases you really donβt need to do it manually. Because when you get to a job especially with that many years left until, they are going to demand you use AI for efficiency and not care about the methods.
I find that the best way to use AI is to treat it like a very enthusiastic teenage subordinate. Delegate things to it, but assume it will make mistakes, or take shortcuts to preserve its own ego. Give detailed, precise instructions, and be prepared for it to make incorrect assumptions.Verify everything it does, and know that you need to have final say and culpability in everything it does.
It's fast and very useful, but you need some skill at wrangling it.
And, like you said, it's far more powerful as a partner to bounce ideas back and forth with while you do the actual work, than it is when you just tell it to do something.
And yes, AI being implemented into workflows is basically inevitable. Doing it correctly will be the trick.
Also like teenagers, they have no persistent memory of things you taught them! You have to repeat your specifications and rules everytime it cleared its cache, you'd thought no imaginary sources should have been default but Noooo you have to repeatedly tell it not to lie
Exactly. Enthusiastic, but in need of constant direction and guidance.
A big advantage over actual teenagers is they won't get pissy if you tell them to start over and do it all from the top. Which is an important thing to do. Trying again fresh, or pitching the question at a different LLM is a good sanity check when you can't personally verify something that sounds plausible. If it's a hallucination, it will be different each time.
I use AI a lot now. I find itβs best used when you can essentially interrogate it a bit against your own intelligence and use it for data collection, mathematical modeling, or coding tasks that you might could have actually done yourself but often wouldnβt have because the time constraints would have been immense.
An 11 year old wouldnβt catch on to that, but in their terms if they were going to use ChatGPT to write a paper for school, you have to be smart enough to not just put βwrite a 500 word essay on why white people are badβ but instead need to think to follow up going back and forth with it, have it add a spelling or grammatical error somewhere, make sure it looks like an 11yo wrote it and not a college student, etc. Beyond shaping output, if you ask me, in a lot of cases you really donβt need to do it manually. Because when you get to a job especially with that many years left until, they are going to demand you use AI for efficiency and not care about the methods.
I find that the best way to use AI is to treat it like a very enthusiastic teenage subordinate. Delegate things to it, but assume it will make mistakes, or take shortcuts to preserve its own ego. Give detailed, precise instructions, and be prepared for it to make incorrect assumptions.Verify everything it does, and know that you need to have final say and culpability in everything it does.
It's fast and very useful, but you need some skill at wrangling it.
And, like you said, it's far more powerful as a partner to bounce ideas back and forth with while you do the actual work, than it is when you just tell it to do something.
And yes, AI being implemented into workflows is basically inevitable. Doing it correctly will be the trick.
Also like teenagers, they have no persistent memory of things you taught them! You have to repeat your specifications and rules everytime it cleared its cache, you'd thought no imaginary sources should have been default but Noooo you have to repeatedly tell it not to lie
Exactly. Enthusiastic, but in need of constant direction and guidance.
A big advantage over actual teenagers is they won't get pissy if you tell them to start over and do it all from the top. Which is an important thing to do. Trying again fresh, or pitching the question at a different LLM is a good sanity check when you can't personally verify something that sounds plausible. If it's a hallucination, it will be different each time.