Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for feedback: AI Assisted Configuration #298

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

nielsmaerten
Copy link
Owner

New: AI Assisted Configuration

Intent

Configuration is the hardest part of setting up ynab-buddy. This PR aims to make that process easier with... AI (because duh).

The config file can be daunting for users unfamiliar with csv parsing, date formats, and so on. In an attempt to make configuration easier* I'm suggesting this update to the config file.

What it does

I'm adding a new section to the config file. Humans can completely ignore it, but if the config file (along with this new section) gets pasted into ChatGPT, Claude, Gemini, ... it will instruct the AI assistant to help the user set up their own config file.

Testing

So far, I've tested this on GPT-4o and Claude 3.5 Sonnet. Both provided adequate guidance in setting up a config file.

Caveats

The AI assistant should warn the user not to share sensitive information, such as their YNAB personal token, or plain transaction files. Both GPT-4o and Claude 3.5 Sonnet followed these instructions well.

Request for feedback

If you're reading this, you can help me! Copy the new config file from this PR, and paste it into your favorite AI chatbot. Let the bot guide you through creating a new config file, and note how it performs (both the good, the bad and the ugly)


* (and because you can't really be a software developer today without adding some AI-flavor)

@nielsmaerten
Copy link
Owner Author

Calling all contributors! 🎉 @kenlim @iofjuupasli @tobim-dev @ahmedmsvb

Hi guys, hope you're doing well.
If you're up for a little AI-experiment, I'd love to hear your feedback on this suggestion.

No pressure at all - this is totally optional and there's absolutely no rush.

@nielsmaerten nielsmaerten marked this pull request as ready for review August 28, 2024 13:05
nielsmaerten

This comment was marked as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant