-
Notifications
You must be signed in to change notification settings - Fork 2
Working on your own & show-and-tell chapters #67
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
Conversation
…ganize sections for clarity and add new tips for effective learning and collaboration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should specifically, maybe repeatedly, remind people to git add . (and commit when each step is working) between prompts. It's really important to be able to see exactly what the LLM is changing with each prompt and if the changes all mix together it can be overwhelming to understand why it did what.
We can even suggest they record the prompt in the commit message (but then we have to suggest not using -m, a new concept, and edit the commit in an editor)
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ktaletsk these updates are great!
Co-authored-by: Rosio <[email protected]>
Co-authored-by: Rosio <[email protected]>
Co-authored-by: Rosio <[email protected]>
|
I am going to merge and address the remaining comments in a separate PR (#92) |
🔍 Preview: https://jupytercon2025-developingextensions--67.org.readthedocs.build/
Note: This Pull Request preview is provided by ReadTheDocs. Our production website, however, is currently deployed with GitHub Pages.