When i buy 512G microsd it becomes my property. If i need to repair or replace my property, it should be disclosed what technology i bought, so that i or my repairman could understand my property enough to decide a proper path forward depending on my data & other environmental devices.
The author needed to reverse engineer what could have been on the spec sheet...
Step 1: curate a context window of code from different repos (poke team about switching to mono repo)
Step 2: write a slack style message as if you are discussing the solution with a teammate that you have authority over as a delegate to get shit done & to revise as needed.
Step 3: press enter, LLM does something you don't like, delete history, fix prompt in step 2 and ask again, rinse and repeat until you have working code.
Step 4: ask for the changes to be written as a bash file that cat EOF all the files that change into place, run the script.
Step 5: git diff & play test the changes using functional testing (use your mouse & keyboard test the code paths that changed...)
Step 6: continue prompting & deleting history as needed to refine.
I was just thinking about something like this for very small web applications (1,200 line app.py & 600 lines of html templates), something lighter than requiring a working docker install.
a handful of dependencies (mostly Pyramid based at the moment) & whatever dependencies those have, pull it all down & serve it out of a tarball or zip file of a portable virtualenv.
If the maintainers are reading this is cool. I would start with an exporter/importer for pages from Wikipedia format into whatever format you use, it should also deal with the media. This is no small task but what you need.