aider/examples
Paul Gauthier bb596db9e4 copy
2023-05-14 15:11:48 -07:00
..
2048-game.md copy 2023-05-14 14:32:12 -07:00
complex-change.md copy 2023-05-14 15:11:48 -07:00
css-exercises.md copy 2023-05-14 14:32:12 -07:00
hello-world-flask.md copy 2023-05-14 14:32:12 -07:00
pong.md copy 2023-05-14 14:32:12 -07:00
README.md copy 2023-05-14 14:47:56 -07:00
semantic-search-replace.md copy 2023-05-14 14:32:12 -07:00
update-docs.md copy 2023-05-14 14:32:12 -07:00

What's it like to code with GPT-4?

Below are some chat transcripts showing what it's like to code with the help of GPT-4. They were recorded using the aider command line tool. In the chats, you'll see a varity of coding tasks like generating new code, editing existing code, debugging, exploring unfamiliar code, etc. It's worth noting that:

  • Each time GPT-4 suggests a code change, aider automatically applies it to the source files.
  • After applying the edits, aider commits them to git with a senisble commit message.
  • aider notes each time a source file is added to the chat session. Once added, these files are available for review and editing by GPT-4. The user adds files either via the command line or the in-chat /add command. If GPT-4 asks to see specific files, aider asks the user for permission to add them to the chat.

Chat transcripts of coding sessions with GPT-4

Transcript formatting

Output from the aider tool is shown in a blockquote like this.

> The user's chat messages are bold and shown on a prompt line like this. They contain they user's change requests, clarifications, etc.

Responses from GPT-4 are in a plain font like this, and often include colorized "edit blocks" that specify edits to the code. Here's a sample edit block that switches from printing "hello" to "goodbye":

hello.py
<<<<<<< ORIGINAL
print("hello")
=======
print("goodbye")
>>>>>>> UPDATED