Fake building: Claude wrote 3k lines instead of import pywikibot
fireflysentinel.github.io
fireflysentinel.github.io
https://www.pangram.com/history/dee030c0-0362-43d0-8fbd-bbab...
1) Let people know that you did that
2) Try to include a link to another page, which shows the prompt and your original version of the writing, even if it is in your native language
This will help people understand what you wanted to say.
Edit: The fact that you used AI to write your post, when your post is saying that you can’t trust AI to do a good job, is… super ironic lol :)
Meanwhile, those who continue to read unprejudiced but with applied critical thinking skills will at least remain in tandem with the red queen.
I think it has less to do with being more conservative and more to do with not losing one of the few remaining ways to see the personality of other tech people.
I do that for most of my docs because I ramble.
I prefer my rambling, but I think others like the tidied up LLM summary.
How does this document score - just wrote it today, used Gemini to sum it up: https://github.com/cuzzo/clear/blob/master/docs/retrospectiv...
https://github.com/cuzzo/clear/commit/8c8a50f1d2c8fa2e8dca64...
On my worst, I rant worse than listening to an LLM.
When I make an effort, my personality comes through at no cost to the reader.
So far I haven't found a prompt that can impersonate me properly. I'm open to it.
Seeding it with a handful of my favorite articles gets me halfway, but the editing is still needed.
On the other hand, if you just tell it to do a thing, I could believe that it would just do the thing. It is pretty bad at high level design judgment. Human guidance on architecture choices results in much better output.
If you want a particular implementation approach, you need to specify not only the features you want, but the implementation strategy at least at a high level. This could be as simple as adding "use pywikibit" or "use relevant packages from pypi" to the end of your prompt. Or you could seed your project with some manually writtem scaffolding, including a pyproject.toml
While LLMs do tend have NIH syndrome by default, I think this is a good default. I'd much rather have tight control over when and how to include external dependencies as opposed to letting a prompt fire for 40 minutes, and coming back to find 2 GB of newly installed node packages with a dependency tree 300 levels deep.
Then, you tell your AI to stick to that rule, and it will. There are tradeoffs to each choice, and people fall into different camps. Make your choice, write it down, and tell the AI to always follow that rule, and then you have it your way.
If you tell it to leverage dependencies, it will. If you (like me) prefer that it avoid dependencies, it will.
The tradeoffs are very different with AI code than human written code. There are still tradeoffs, but they are different now.
This kind of incremental addition without planning in advance leads to inconsistent code with lots of redundancies.