213 karma · joined August 29, 2020
I may not have the luxury to ignore bad incentives right now, but I try to make lemonade from the lemons life throws at me so that one day I can.
So, is there a way to train a neural network and then tune it forget a lot of the facts that can be easily retrieved, but keep the intelligence.
I felt this was a much better layman explanation of what a quantum computer does than simply saying a quantum computer runs all possible paths in parallel.
A quantum computer is such a macroscopic state.
I don’t claim to understand them though. I have tried.
Maybe what I meant was this: if I perform a quantum experiment where the spin measurement of an electron could be spin up or spin down, the future me would end up in one of two branches: I measure spin up, or I measure spin down. There wouldn’t be any possible world where I measure a superposition of spin up and spin down, because such a a state is going to decohere rapidly. This makes sense. What I’m unable to grasp is that even though the wave function of the universe contains both branches, “I” somehow experience only one of the two branches.
The answer to that I guess if that the two branches are nearly orthogonal they will merrily evolve independent of each other. But somehow “I” only experience only one of them.
Sorry for the rambling. I’m not able to articulate what I don’t understand.
The Stanford Encyclopedia of Philosophy (https://plato.stanford.edu/entries/qm-manyworlds/) goes into this in some depth, and it seems like the right way to think about it is say that "I" in one branch is a different entity than the "I" in a different branch. I have somehow not been able to grok it yet.
And I agree about the naming. I really dislike the name "many worlds interpretation", which seems to imply that we have to postulate the existence of these additional worlds, whereas in fact they are branches of the wavefunction exactly predicted by standard quantum mechanics.
Maybe the train is software that's built by SWEs (w/ or w/o AI help). Specifically built for going from A to B very fast. But not flexible, and takes a lot of effort to build and maintain.
That would force the programmer to remove the std::move, making it clear that its a copy.
auto var = FunctionCall(...);
Then, in the IDE, hover over auto to show what the actual type is, and then replace auto with that type. Useful when the type is complicated, or is in some nested namespace.
Any software engineer who shares this sentiment is doing their career a disservice. LLMs have their pitfalls, and I have been skeptical of their capabilities, but nevertheless I have tried them out earnestly. The progress of AI coding assistants over the past year has been remarkable, and now they are a routine part of my workflow. It does take some getting used to, and effectively using an AI coding assistant is a skill in and of itself that is worth mastering.
For spec driven development to truly work, perhaps what’s needed is a higher level spec language that can express user intent precisely, at the level of abstraction where the human understanding lives, while ensuring that the lower level implementation is generated correctly.
A programmer could then use LLMs to translate plain English into this “spec language,” which would then become the real source of truth.
In feedback systems, the gain is a function of frequency, and typically decreases when going from low frequency to high frequency. This is often accompanied by a phase delay.
So if the overall gain of the system is high enough, there will be some high frequency where the gain is 1, and the phase is 180 degrees. This would result in positive feedback, amplifying noise at that frequency.
Maybe that’s what’s happening in the latest AirPods? If Apple is aggressive cranking up the gain of the noise cancellation system, there’s some high frequency where the noise gets amplified rather than suppressed.
The solution would be to either reduce the gain (which reduces the noise cancellation), or to add some differential gain in the system which pushes out the unity gain frequency to higher frequencies.
A simple solution would be to mandate that while posting coversations with AI in PR comments is fine, all actions and suggested changes should be human generated.
They human generated actions can’t be a lazy: “Please look at AI suggestion and incorporate as appropriate. ”, or “what do you think about this AI suggestion”.
Acceptable comments could be: - I agree with the AI for xyz reasons, please fix. - I thought about AIs suggestions, and here’s the pros and cons. Based on that I feel we should make xyz changes for abc reasons.
If these best practices are documented, and the reviewer does not follow them, the PR author can simply link to the best practices and kindly ask the reviewer to re-review.