Devin credit used up 4/23 Inventory
Devin credit used up 4/23 Inventory
It's not good that the Devin order placed the day before yesterday has not been resolved.
What's left.
Analysis of the ability to state the approximate time it takes to output a report.
We could collect information on the time
Trouble where to collect length of comments
I think example-polis is GitHub LFS.
Devin and I got confused about the fix for this.
Discard.
Ability to duplicate and reuse reports
I thought it was not good enough to test it without implementing it up to step2, so I decided to record the report and move on.
TODO: waiting for step2 implementation
When displaying dense clusters, the cluster description is also displayed together.
TODO: Human test town
Display the cost of processing it during CSV upload
Commentary.
Explanation Page Execution Plan Creation
I decided to have it implemented.
week 6
I let run.sh run.
It's better to let Devin do it than to share the errors you've run into and fix them on your end.
Why did he reveal the "collective processing" of the lidobata?
Because you didn't merge PR36.
I merged 36 and 38 was conflated.
Let's get it fixed.
✅
(Experimental) embedding-based preprocessing
Pointing out that this is the most important
Yeah, maybe.
Devin implementation in progress
Implementation is ready.
Testing is required
Report automation hasn't worked out yet.
make him mend
History of BROJECT
Transcription transcription
Code quality improvement
I got conflicts because I didn't merge right away.
Public Opinion Map OSS-ization, stopping at the point where I write the README.
---
This page is auto-translated from /nishio/Devinクレジット使い切り4/23棚卸し using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.