It may be an opinion, but pointing it out won't make me like java any more.
If I find myself repeating more than twice, I just ask "Can this be a function". If yes, I move it there. If not, I just leave it as it is.
Life's too short to spend all day rewriting your code.
Yes, but also I would hope that if you have the autonomy to install linux you also have the autonomy to look up an unknown command before running it with superuser privileges.
If you want a pretty cool example, Le morte d'Arthur was written in prison.
They're definitely among the worst of the worst. It's always surprised me how comparatively sterile their wiki page is. Feels like they've got someone cleaning it up.
Three cents for every 1k prompt tokens. You pay another six cents per 1k generated tokens in addition to that.
At 8k context size, this adds up quickly. Depending on what you send, you can easily be out ~thirty cents per generation.
Claude 2 isn't free though, is it?
Either way, it does depends on what you want to use it for. Claude 2 is very biased towards positivity and it can be like pulling teeth if you're asking it to generate anything it even remotely disapproves of. In that sense, Claude 1 is the superior option.
Presumably you watermark all the training data.
At least, that's my first instinct.
You can make it as complicated as you want, of course.
Out of curiosity, what use-case did you find for it? I'm always interested to see how AI is actually applied in real settings.
Lazy is right. Spending fifty hours to automate a task that doesn't take even five minutes is commonplace.
It takes laziness to new, artful heights.
True! Interfacing is also a lot of work, but I think that starts straying away from AI to "How do we interact with it." And let's be real, plugging into OAI's or Anthropic's API is not that hard.
Does remind me of a very interesting implementation I saw once though. A VRChat bot powered by GPT 3.5 with TTS that used sentiment classification to display the appropriate emotion for the text generated. You could interact with it directly via talking to it. Very cool. Also very uncanny, truth be told.
All that is still in the realm of "fucking around" though.
That's only the first stage. Once you get tired enough you start writing code that not even you can understand the next morning, but which you're loathe to change because "it just works".
"The bug is fixed, but we inadvertently created two new ones, one of which broke production because it was inexplicably not caught."
If you want to disabuse yourself of the notion that AI is close to replacing programmers for anything but the most mundane and trivial tasks, try to have GPT 4 generate a novel implementation of moderate complexity and watch it import mystery libraries that do exactly what you want the code to do, but that don't actually exist.
Yeah, you can do a lot without writing a single line of code. You can certainly interact with the models because others who can have already done the leg work. But someone still has to do it.
It really is big. From baby's first prompting on big corpo model learning how tokens work, to setting up your own environment to run models locally (Because hey, not everyone knows how to use git), to soft prompting, to training your own weights.
Nobody is realistically writing fundamental models unless they work with Google or whatever though.
Der Prozess/The Trial is one of the better ones in my opinion. Really captures the essence of Kafka. Of course, it is also one of his longer works.
I've used WSL to run deepspeed before because inexplicably microsoft didn't develop it for their own platform...
I read it a long time ago. The format is interesting, novel certainly. I suppose it's the selling point, over the prose.
To me it seemed like there were many competing "ways" to read it as well. Like a maze, you can go different paths. Do you read it front to back? Niggle through the citations? Thread back through the holes? It's not often you get a book that has this much re-read value.