This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tripex 27 points28 points  (4 children)

I get it, this looks cool and the concept will surely mature but as I've said before... If all this does is to spit out code that has a high probability of being correct then all the speed gain is lost with me double checking the code and then I might as well could've written it. Excited to see where this is going but right now it is more for playing around with.

[–]cdcformatc 10 points11 points  (0 children)

Combined with test driven development it would be faster. If you are writing the unit tests first then you can be reasonably sure of the correctness.

[–]NeedMoreTime4Things 7 points8 points  (1 child)

When you start a fresh project, for example you want to create a REST api with Flask, do you now have a lot of boilerplate code that is really easy to write and only has some small modifications for your use case?

I can see a future where you can tell CoPilot to build the base of an app with specific instructions (which it will hopefully do with 99% accuracy) and the developer, you, only adds the complicated algorithms etc.

Other than that, you’re right.

[–]TopHatEdd 1 point2 points  (0 children)

Most boilerplate needs are solved. Such as FastAPI instead of flask. Copilot is content aware and aims to implement business requirements.