25 ms·
I can see this being useful already (assuming context length is not an issue) as some sort of github service trying to solve github issues throughout the day.
by CapsAdmin 3y ago
I can see this being useful already (assuming context length is not an issue) as some sort of github service trying to solve github issues throughout the day.
Or for example if you commit todo's in your code, the ai will pick up on them and give you some options later on.
If the failure rate is 14%, just let it try a bunch of times. (half joking here)
The way I see it is at least the project issues are getting some attention, which is arguably better than no attention. If it can just fix simple things, at least you can focus on the complex things and not worry about postponing the low hanging fruits.
- samstave 3y agoWhat about Youre Holding It Wrong? IE: Maybe rather than throwing it find problems, also use it to just build things from scratch - as an example: The side hustle: make that a product: Let someone like me who is not a coder have access to Devin for a month with the only goal of building a side hustle that brings a solo person a monthly income. Then - Sell that so that the millions of people who have a solo idea and just need that "technical co-foumder" can use it to build. and limit it to one devin instance to a person to start... I dont want it to do a one fell swoop - I'd like to say "build this module... -- Have a contest where you get What can you build with Devin in TOPIC in 30 mins.
- HarHarVeryFunny 3y agoI could perhaps see more value for this, at this level of capability, in writing test cases, in cases where the project is setup in a way to let them be run and get feedback. This would be useful in cases where test coverage is incomplete, maybe for auto-discovering/confirming bugs, and would really be needed if it's trying to fix bugs itself, especially if one dared let it commit bug fixes - would want to know that the fix worked and didn't break anything else (regression test - run other test cases too).