Repository navigation
AI usage memo #1624
Description
recipes, from time-consuming experience
errors:
- prompting too simple: the AI doesn't respect any rule and can change things you don't want at first (like variable names)
- not using multi-AI loost the comparison and compensation (like orthographic errors, what is generated different is what to look)
- an easy before/after comparison test is usefull, better when they can auto-check themself, simpler if they write auto-test
- not adding safe exit to llm , "do you think it's possible ? is there enough information to", may reduce hallucinations
- accepting torents of lines of code... as AI can bloat you also on this
total time saver:
- asking AI to not disrupt existing code: "can you help rework it so it can do current feature and new one ?"
next level things:
- GitHub Copilot for Skeptics Who Still Think AI is Overrated: explains some AI beginner errors
This parodic picture summarizes well the standard pitfalls when using IA too blindly
Activity
stonebig commentedon May 30, 2025
diff.py:
let's try to use AI in a smarter way:
- run current and proposals from openai, copilote, mistralai, gemnicodeworks
- compare results (accept slight massage at interface naming, output must be same as original)
- compiles without hurting much interface: openai,, gemini
- don't crash and result ok: openai,
- crash and burn : gemini, mistralai
- change interface (remove a parameter): copilote
- lines_of_code (ignoring commente of gemini): original: 170 , openai: 129, copilote: 98, mistralai: 161, gemini: 350
in the end, still 1 day to:
- digest the AI change
- then do the re-engineering to move diff.py down
stonebig commentedon May 31, 2025
package_index_markdown (try on copilote, as move of code between the project files)
proposed the stupid/basic solution, good here
stonebig commentedon Jun 1, 2025
adding safe exit to llm , "do you think it's possible ? is there enough information to", may reduce allucinations
to copilote:
could we make piptree working either on current installeed packages, either in a directory of packages ? it seemes all we need is reading the metadata from the archive like wheelhouse.py doesgives a general structure that works, but prefer doing integration by hand so far
stonebig commentedon Jun 7, 2025
asking an AI (copilote github) to take care not disrupting existing code... does work!
stonebig commentedon Jun 29, 2025
the two most eminent uv people use AI (typically Claude, at the moment)... maybe also because with AI, the slowness of alternatives becomes the main time-loss/cost factor in their workflow.
Agentic Coding: The Future of Software Development with Agents