|
|
|
|
|
by porridgeraisin
1040 days ago
|
|
Yeah, and while it's true it can't really solve something you have to think about specific to your problem domain, I find it really good for common implementations. If I'm making a music app and I'm implementing shuffle, I just type function fisherYates(arr: IPlaylistItem[]) { tab
and it's done. Similarly, I just type class SortedSet:
// api has to have add, rank, cardinality, itemsinrange(make this a fluent api with min max fns returning self each time, and a get to resolve it, and items() to start it)
// use redis
And it does the zrank, zcard zadd etc figuring out how to call the py-redis API.Similarly I cba when learning an ORM to find out how specifically it does something by scouring it's docs, I just type SQL or natural language there or the beginnings of it atleast, and let copilot fill out the orm api for me. After which I can just hover over the functions it chained/nested together and the docs pop up and I verify that it did it right, and read any caveats they mention. I pretty much learnt how to use prisma just by seeing what copilot produced. |
|