Posted: Aug 25, 2025 9:35:49 pm
|
|

Posts: 137
Registered:
2013-12-25
|
General concepts in working with AI
So far in my working with AI it's been very good basically I use perplexity and deepseek. Deepseek seems a little bit more capable. When the projects are small I can send all the code back and forth to deep seek and in order to bring deep seek up to speed I need to send him the code so by keeping everything in one big file all the Java the CSS the html it's easy to do call when the files get bigger then the system between AI and I starts to choke and we've been having problems. Perplexity has been dropping the ball a little bit making kind of gross errors that even I can pick up so just saying.
One of the projects on the drawing board currently is a scanner program or it would be a tool that deep sequence help me make or perplexity either one or both and it would go through and scan all my source code zip it up in a nice little file and send that to the AI and then the AI can unzip that and know where everything is and know what's gotta be done and then if I need to deal with files I could just have my files broken down into smaller units and and that's kinda how I expect to go.
But for the moment we're gonna use everything in one file to keep it easy because I don't gotta scan a program yet to do that. So in the mean time I will send currently the vector program is the one that's the largest HTML file with all the source code in it 50K seems to be the limit of what I can send and what deep seek or perplexity can sit back is even less than that but if they send it in chunks that usually works so what we've been doing is all upload the html file to the vector tool in two parts keeping it under 50K I send roughly half and half two files and then I am gonna have deep seek have comments in the file or breaks that instead of meat replacing the whole entire file I could say I need this and that done on my program and he would say ohh that's in section two and 7 so he would just replace those sections of code and it would be very simple and kind of handle it that way. Hear the thoughts from deep seek how he proposes to do it.
Here's My Plan:
Add compatible section markers to your electrical vector tool
Test thoroughly to ensure no errors are introduced
Send you the organized version with clear, safe markers
Use this approach on your other projects so we both get practice
The Beautiful Part:
Once we have this system in place:
You'll describe changes in plain English: "Make the buttons bigger" or "Fix the calculation bug"
I'll instantly know which sections need updating
You'll copy/paste just those sections
Everything will work without mysterious errors
Let's Do This Right:
I'll carefully add section markers using proper HTML/JS/CSS comment syntax that won't break anything. The markers will be obvious and easy to find but completely invisible to the browser.
This time next week, we'll look back at this as the turning point where we went from struggling with big files to having a smooth, reliable workflow!
Shall I get started organizing your electrical vector tool with the new section markers? This is going to be a game-changer for all our projects! 🚀
|