What I am about to demonstrate:
Building a custom AI Chat Assistant that is written in ReactJS and NodeJS without writing any code at all. It will all be handled by a new AI Automation Coding API Blaze Engineer. What will be built in the demonstration can easily be extended and/or modified.
Prerequisites - Which I have already completed:
- Created an account at Blaze Engineer.
- Logged into Blaze Engineer to access my Auth Token.
- Generated a SSH Private/Public Key
- Added SSH Public Key To Github Account
- Added SSH Private Key To Blaze Engineer Account
- Wrote two Blaze Engineer Coding Job Tasks.
The first Blaze Engineer Coding Job Task is huge because it defines the base design/architecture/features for the new project.
The second Blaze Engineer Coding Job Task is small because it is simply adding a new small feature to the just created new project.
Here is the brand new Github Repository before the initial Blaze Engineer Coding Job runs:
- Left = Two Blaze Engineer Code Job Task Definitions in Notepad
- Center = Blaze Engineer API Playground
- Right = Brand New Github Repository
Before we can run the initial coding job on the brand new Github repository we must add the new repository to list of usable repositories in Blaze Engineer:
Now that we have added the new repository to Blaze Engineer. We can now run the initial coding job on the brand new repository. This is how you setup running a new job:
This is the response from running a new job:
Here is the Github files changes from the initial coding job:
Here is adding an additional new feature to the code base we just generated in the first coding job:
Here is the Github files changes from the add additional new feature coding job:
Here is the file changes in more detail:
Other ways of tapping into Blaze Engineer
HTTPS API
NodeJS Client Library NPM Package
Interactive CLI Tool NPM Package
Here is the Blaze Engineer API Automated Coding/DevOps Workflow Flow Chart:
We have it setup so when a task gets dropped in a certain list in our Task Board application it triggers a /jobs/run request, then waits for the request to complete, then run tests, then if the tests pass, it deploys, and then it will move the task in the Task Board to the Completed By Blaze Engineer list.
Conclusion
Writing the Coding Job Tasks is the most time consuming part of the 15 minutes. Blaze engineer does the rest quick. The initial code sync on a new repository and branch can take a few minutes but future coding job tasks on the same repository and branch will skip code syncing and jump straight to coding.
If the Coding Job Task is written without contradictions, missing critical details, and has enough details of the user's vision, it should with a high success rate do a good job of providing a good outcome.
Blaze Engineer just reached beta. So we have not got around to getting everything we can to make the costs as cheap as possible completed yet but we will. The cost right now are reasonable but we can make it even better!
We're looking for JavaScript/TypeScript engineers to test out the Beta of Blaze Engineer. If testing out Blaze Engineer sounds interesting to you then apply for beta access at Blaze Engineer and your application should be reviewed quickly. If granted access you will be emailed an beta key plus an invite to the Blaze Engineer Discord.
Happy vibe coding the easy way!
- The Blaze Engineer Team
Top comments (0)