I've not used it on any team projects, so I can't speak to that.
I don't know how valuable it is to retrain after small changes to the code. Obviously if small changes don't matter then it can be rarer, and if they do then it should be more frequent. I would like to feel like it's always up to date and Just Workstm without having to worry about that. To that end, I would like to have it updating on my local machine as changes happen, at whatever frequency makes sense.
I don't know what analysis is being done, but could it be iterative as changes happen or does it need to do a full rebuild every time?
My solution that comes in at around 5,000 lines takes about a minute to train. If that number is much larger for bigger solutions, then having the ability to train it on a server through CI or nightlies and pull it down from clients is important. I would like to see both workflows be supported and complementary.
I build developer tools and services at Microsoft (currently Codespaces, Live Share, IntelliCode) and maintain some OSS projects (CodeTour, GistPad, CodeSwing, WikiLens)
I can’t thank you enough for sharing this detail! Would you be open to setting up a quick chat sometime this week? You’re giving some amazing feedback, and I know that our team would love to learn further about your experiences 😁 If so, feel free to ping me (joncart@microsoft.com) and we can go from there 👍
I'd be happy to, but I'm not sure that I have that much great insight. I've been using it casually on a medium sized personal project - a suite of Roslyn analyzers - but I've not thought about it in too much detail, other than what I've posted here. Would it be easier if I just keep posting things here when I think of them?
I build developer tools and services at Microsoft (currently Codespaces, Live Share, IntelliCode) and maintain some OSS projects (CodeTour, GistPad, CodeSwing, WikiLens)
I've not used it on any team projects, so I can't speak to that.
I don't know how valuable it is to retrain after small changes to the code. Obviously if small changes don't matter then it can be rarer, and if they do then it should be more frequent. I would like to feel like it's always up to date and Just Workstm without having to worry about that. To that end, I would like to have it updating on my local machine as changes happen, at whatever frequency makes sense.
I don't know what analysis is being done, but could it be iterative as changes happen or does it need to do a full rebuild every time?
My solution that comes in at around 5,000 lines takes about a minute to train. If that number is much larger for bigger solutions, then having the ability to train it on a server through CI or nightlies and pull it down from clients is important. I would like to see both workflows be supported and complementary.
I can’t thank you enough for sharing this detail! Would you be open to setting up a quick chat sometime this week? You’re giving some amazing feedback, and I know that our team would love to learn further about your experiences 😁 If so, feel free to ping me (joncart@microsoft.com) and we can go from there 👍
I'd be happy to, but I'm not sure that I have that much great insight. I've been using it casually on a medium sized personal project - a suite of Roslyn analyzers - but I've not thought about it in too much detail, other than what I've posted here. Would it be easier if I just keep posting things here when I think of them?
Sure! That would be great
I will do!