Difference between revisions of "AI usage framework"
From MSX Game Library
(Created page with "Here is the framework established regarding the use of AI in the development of MSXgl. I distinguish between three different levels of AI usage: == đ€ Vibe coding == Let t...") |
(ââđ§âđ» Human scale) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Here is the framework established regarding the use of AI in the development of MSXgl. | Here is the framework established regarding the use of AI in the development of MSXgl. | ||
| â | + | The author distinguishes three different levels of AI usage: | |
== đ€ Vibe coding == | == đ€ Vibe coding == | ||
Let the AI do its thing without trying to understand the details of the generated code, as long as it gets the job done. | Let the AI do its thing without trying to understand the details of the generated code, as long as it gets the job done. | ||
| â | Reserved solely for experimentation on projects that aren't essential to MSXgl and that | + | Reserved solely for experimentation on projects that aren't essential to MSXgl and that simply would never have existed otherwise: |
* MSXgl Project Wizard | * MSXgl Project Wizard | ||
== đŠŸ AI assisted == | == đŠŸ AI assisted == | ||
| â | + | Develop with the help of AI while maintaining control over the entire codebase. AI is there to provide support for specific needs, and while it can generate code, that code is integrated into the program only if it is fully understood in detail (manual integration is preferred). | |
| â | + | Reserved for projects not directly related to MSXgl, in which the author has an interest but on which he does not wish to spend too much time so as to focus on the essentials: | |
| â | * | + | * [https://github.com/aoineko-fr/MSXgl/tree/main/tools/MSXtk MSX Tools Kit] (MSXimg, MSXbin, MSXhex...) |
| â | * [https://msx.org/mgs MSX Game Score] | + | * [https://msx.org/mgs MSX Game Score]'s web site |
== đ§âđ» Human scale == | == đ§âđ» Human scale == | ||
| â | Made entirely by hand to maintain total control over the code, work at | + | Made entirely by hand to maintain total control over the code, work at its own pace, and challenge itself. That's what the author loves about MSX development, often even more than the final result. AI can be used to gather information, handle formatting, or provide comments, but it doesn't write a single line of code (as has been the case for several years now). |
This concerns the core of MSXgl: | This concerns the core of MSXgl: | ||
* Library modules | * Library modules | ||
* Build tool | * Build tool | ||
| â | * | + | * MSX games |
| + | |||
| + | |||
| + | If anyone would like to contribute to MSXgl, the author is counting on them to respect this approach and submit only code they've written themselves. | ||
| + | |||
| + | AI is extremely powerful and can do so much in an instant that the author can understand why it might be tempting to use it to meet the needs of your projects. Since MSXgl is an open-source project, please feel free to create your own fork and improve it with AI however you see fit. | ||
| + | |||
| + | However, the author is counting on users to follow one rule: don't ask him for help with code created or modified by AI. His pleasure lies in creating code for humans, not from fixing code created by AI. | ||
| + | |||
| + | [[image:Twonks ai.png|400px]]<br/><small>by [https://www.instagram.com/twonks Twonks]</small> | ||
Latest revision as of 00:35, 28 October 2026
Here is the framework established regarding the use of AI in the development of MSXgl.
The author distinguishes three different levels of AI usage:
đ€ Vibe coding
Let the AI do its thing without trying to understand the details of the generated code, as long as it gets the job done.
Reserved solely for experimentation on projects that aren't essential to MSXgl and that simply would never have existed otherwise:
- MSXgl Project Wizard
đŠŸ AI assisted
Develop with the help of AI while maintaining control over the entire codebase. AI is there to provide support for specific needs, and while it can generate code, that code is integrated into the program only if it is fully understood in detail (manual integration is preferred).
Reserved for projects not directly related to MSXgl, in which the author has an interest but on which he does not wish to spend too much time so as to focus on the essentials:
- MSX Tools Kit (MSXimg, MSXbin, MSXhex...)
- MSX Game Score's web site
đ§âđ» Human scale
Made entirely by hand to maintain total control over the code, work at its own pace, and challenge itself. That's what the author loves about MSX development, often even more than the final result. AI can be used to gather information, handle formatting, or provide comments, but it doesn't write a single line of code (as has been the case for several years now).
This concerns the core of MSXgl:
- Library modules
- Build tool
- MSX games
If anyone would like to contribute to MSXgl, the author is counting on them to respect this approach and submit only code they've written themselves.
AI is extremely powerful and can do so much in an instant that the author can understand why it might be tempting to use it to meet the needs of your projects. Since MSXgl is an open-source project, please feel free to create your own fork and improve it with AI however you see fit.
However, the author is counting on users to follow one rule: don't ask him for help with code created or modified by AI. His pleasure lies in creating code for humans, not from fixing code created by AI.
by Twonks