Was there pressure to do this, or freedom to do this? If I had an unlimited token budget I'd probably try all sorts of crazy things. Also you (one) can read the tests and see that they weren't modified to forcibly pass.
Maybe he didn't think it would work. Maybe even if it does "work" they'll keep the zig version anyway. Maybe further study is needed beyond existing compiling/test-suite. Intentions and perspectives change over time, even only a few days, without dishonesty.
I'm guessing that if I said it ... that we have no intention of re-writing in rust ... that what I mean is "we have no intention of spending the extreme cost it would take to rewrite". When I discover the cost model is completely different that changes things.
Not AI generated software -- DYNAMICALLY generated software, like at run time and ongoing. Even in-app directed by the user. This is not a thing that existed before, a degree of customizability well beyond letting the user pick a color scheme or from one of a few layouts or default start screens.
I don't know how good of an idea it would be, product-wise, to give programming level flexibility. I am reminded of greasemonkey scripts, but written in english maybe. Maybe it could be awesome. But Apple is saying "nope. Not interested in exploring this with you. BYE"
Maybe another idea, no idea if this is a thing, you could pick your block-of-layers size (say... 6) and then during training swap those around every now and then at random. Maybe that would force the common api between blocks, specializaton of the blocks, and then post training analyze what each block is doing (maybe by deleting it while running benchmarks).
This was not my experience. For example, it want until chromium 110 that you could use webrtc+pipewire without overriding settings, in 2023. So maybe in a strict sense you could do it with fiddling, I don't think you could install any Linux flavor and screen share over meet reliably.
Yep! Maximally closed as much as possible under the law. They also shut down other programs which aim to sidestep propaganda (including US propaganda), though some of those are starting to come back. Radio Free Asia, for example, https://www.reuters.com/world/asia-pacific/radio-free-asia-s...
I've been building a skill to help run manual tests on an app. So I go through and interactively steer toward a useful validation of a particular PR, navigating specifics of the app and what I care about and what I don't. Then in the end I have it build a skill that would have skipped backtracking and retries and the steering I did.
Then I do it again from scratch; this time it takes less steering. I have it update the skill further.
I've been doing this on a few different tests and building a skill which is taking less and steering to do app-specific and team-specific manual testing faster and faster. The first times through it took longer than manually testing the feature. While I've only started doing this recently, it is now taking less time than I would take, and posting screenshots of the results and testing steps in the PR for dev review. Ongoing exploration!
Socials: - github.com/awwaiid
---