You’ve got this big idea for your application. It’s going to be amazing! However, the more pieces you build into it the larger the code base is becoming and the more difficult it is for an AI tool to help without causing other issues.
Component-Based building can help with this a LOT!
Instead of adding on and adding on to one large application, build only one component of that application at a time and then integrate it to the larger application once it’s done.
For instance, if you wanted to build a web-based application for efficient one-stop grocery shopping you will need several components for the finished product. You will need a way for people to log in, their profile account parts, and an interface for them to “shop” on. You will also need to grab the API’s of several grocery shipping services, and also hook up the user accounts in each one.
You could start with the log in interface and that can be the start of the main application.
Then start up another instance of your application (copy) and work on building out more of the user profile.
Once all of that is working, start up a copy of that version (or start up a fully generic instance of your tech framework) and start completely fresh with the API’s or the marketplace view.
When you complete that component, it will be much easier to ask the AI tool to take that code and integrate it with your main application. You might even be able to do a lot of it on your own.
This keeps the AI from touching things that don’t need to be adjusted, and gets even easier if you’re using version control as you will be able to see what files are touched at a glance without needing to keep track of that yourself!
(Check out my version control article here.)
I hope this strategy helps you get more done with less frustration.
If you give this a try leave a comment below to let us know how it went!
Comments