Q: Yes, yes it is but I’d like to ask a follow-up question. I know you said some things about ChatGPT and its flaws but what other thing inspired your solution? You can also share a personal experience or what you know other developers in the community have faced.
Paul: Okay, I can give my personal experiences and pass [the question] on to my team members. So personally and I think generally, I enjoy reading stuff. But sometimes I can get discouraged when I do too much planning before even doing the main thing which can slow down things. So there is an approach that can help you do something way faster, where if you already have a head start, you tend to follow through with what you want to do.
So in this case, now you have an idea [and] you want to build a website for your blog. You probably may not be too proficient in HTML, CSS, and the like but if you can just prompt a tool, say there is a tool that can help you to generate a code to get started. And you just have to follow. Since you have a code to start with, you just continue working and all — So one of the things that inspired this, is you have your IDE where you are coding and you have an AI assistant right there and it’s helping you to achieve what you want to achieve.
Victor: So for the hackathon, Paul essentially brought most of the idea. In terms of my own experience, as an ML Ops, I can completely relate to those problems; writing docs, writing code, Debugging, etc. The tools essentially help write better code.
Dunsin: Yes, so a lot of times when I’m coding and I get errors, I tend to copy the errors inside the terminal and paste it on Google a lot of time it’s usually frustrating searching for errors. And it was more like okay, if there is a tool that can actually just explain an error instead of going from one tab to another so that it will be easy. Whenever I paste code inside Google, Google does not understand the context from which this code is coming. I only paste the error, I can’t paste the whole code on Google search. So I mean, it makes more sense that fixing errors and explaining errors come from the VS code terminal. So I loved that something like this could be done so I tried to work on this. Then, there’s generating code documentation. So, a lot of time, I don’t put README on code and when I get back to it, I will be like “Where do I start from?” — so it just makes things easier. When we have something like documentation even I will be able to understand what I’ve written in the past. So I think that was the main inspiration for this project.