I see this fitting into my workflow more ephemerally. That, or I will use screenshots in some of my existing documentation so it can all rot in one place.
When using an agent for development, I find that I REALLY miss being able to "see" the shape of the code in my head while I work, and I find that I get bombarded with so much information that I cannot keep track of what the code looks like. This has led to me having to get back to people async on questions they have on a call, etc., because I can't remember exactly how i made something work in the end!
I will be using this to make sure I understand my own output at a depth I can remember, and I will be using it to do the same for reviewing complex PRs or diving into new parts of the codebase.
Defense in depth is a thing. There should be audit requirements to show that you have done your due diligence in ensuring that the training environment is locked down.
Spoken like someone terminally online & without children. If this is your view of reality (I believe it is an utter fiction but nonetheless), then I don't know how you propose things to be improved without smart people procreating.
After I entertain you by doing that, is there a steelman version of my reply you're interested in entertaining me with, by replying? Or, just the strawman?
Anything but a log scale would be misleading. When showing long term growth of something that has grown so drastically, it is imperative to use a log scale so that 10% gains look consistent over time. Especially in finance.
When using an agent for development, I find that I REALLY miss being able to "see" the shape of the code in my head while I work, and I find that I get bombarded with so much information that I cannot keep track of what the code looks like. This has led to me having to get back to people async on questions they have on a call, etc., because I can't remember exactly how i made something work in the end!
I will be using this to make sure I understand my own output at a depth I can remember, and I will be using it to do the same for reviewing complex PRs or diving into new parts of the codebase.
reply