On: Building a back end using only OpenAI Codex

[zegl]

It’s hard to say, since I was writing the blog post in parallel as I was making the app. But not too long, maybe an hour or two? I’m not a Python/Flask developer, so I guess that’s not too bad.

[lxe → zegl]

You can also use gpt3 to write most of the blog content. I'm willing to bet soon this is going to be everyone's workflow.

[trention → lxe]

Why would I want to read a blog post written by an AI about a program written by an AI besides novelty? The moment an input in a medium becomes primarily AI-generated is the moment I stop using said medium.

[lxe → trention]

Because you would not be able to distinguish whether a paragraph is written by AI or not. It's not novelty, it's utility.

[trention → lxe]

As I said, if I can't distinguish it, I will stop reading "it" at all. There is no utility in reading text that is not human-generated.

[w1zzy → zegl]

Thanks for info. I am gathering information about efficiency of using code generators. Btw. Nice work!

[verdverm → w1zzy]

I have a non-AI code generator if that would be of interest to your info gathering. It's definitely meant for developer efficiency over the entire software lifecycle. Happy to tell you all about it if you are doing interviews, calls, or the similar.

https://github.com/hofstadter-io/hof | https://docs.hofstadter.io

[teslelover_12 → w1zzy]

yup its really cool