Standard R.A.M.P. update today.
For reading, I’ve been reading a lot about GPT-3 and AI in general. I got a crash course in tokenization today.
For data analysis, I continued testing the Google Docs AI editing project I have been talking about today. It’s not looking good right now, honestly. We’re still trying to figure out if it’s something on Google’s part or if it’s an issue with the code. The results, while accurate and what I would expect, are all over the place billing wise. Something weird is happening when we make the request to the OpenAI API. I should know in the next couple of days whether this project will be successful or if I will have to retire it. We may be able to salvage it…or we may not.
However, I did find out that you can use the OpenAI Playground to test GPT-3’s editing capabilities for yourself. Create a free account, go to the playground, and select “Edit text” from the right-hand menu. This capability is currently free. The biggest downside is you don’t get a list of what changed. This, as I mentioned a few days ago, is the core problem. But you can at least test it.
Work on the second AI editing project using Word and Python hasn’t started yet. That one’s going to be a lot more promising as we will have a lot more flexibility. There shouldn’t be any API issues going this route, either.
For marketing, I did two speaking engagements today—one with the Dallas Romance Writers Association talking about Be a Writing Machine. The second one was with Writer’s Digest as part of their Writer’s Digest University. I talked about keeping promises to the reader. Both were great events.
For production, I’m behind today but that’s because of delving into AI rabbit holes, unfortunately. I should slowly be crawling out of this hole over the next couple weeks and once I do, I should be able to get back to regular production again.
Sometimes you’ve got to slow down so you can speed up.
Have a good night.
