But what if your rubber duck is actually steering your thought process (since you may not have a consolidated one)? In this way I think the AI as editor is far better than a rubber duck AI. While in the former, it might point out your mistakes and give useful advices (which is similar to what you describe), it might not steer your thought (unless your mistakes are far too severe!), and actually help in your reasoning. But AI as a brainstorming rubber duck (or thinking tool) could be harmful to your thought process.
If you let it, sure. But I don't go into a session asking 'what should I write.' Rather, I ask it to help fight me on my ideas, so that I can stress-test the logic behind them, which is precisely what I do with humans too.
Only with humans, it's admittedly way more fun. :)
mine too, but none was such a dick. also, anything related to school (particularly at a young age), is not viewed as something to boast of (at least in my experience in italy, serbia and portugal).
That will be less of a problem since OAI can spill out to other providers as needed if their own capacity is under high utilization. They already use coreweave, aws, azure, etc. Google doesn't do that as far as I know and don't see why they would, so they are stuck eating the capacity planning.
> But the extent and the way in which Zig specifically puts it to use -- which includes, but is not limited to, how it is used to replace other features that can then be avoided (and all without macros) -- is unprecedented.
That MrWhite wanted to knkw an example of Zig's comptime that is not merely a "macro", rather the usage as a replacement of other features (I guess more complex..)
PS just interested in zig, I'd like some pointer to these cool feature :)
so they are basically using a similar idea to that of a stirling engine in thermoelectric generator or they use a different mechanism to produce energy?
Two materials (often n-type and p-type semiconductors) are joined at two junctions, one junction is heated and the other cooled. The temperature difference makes charge diffuse from the hot side toward the cold side, and this charge is what turns into the seebeck voltage they describe. It was just very hard to get anything meaningful out of this because you can't easily get such a temperature difference. If you've read of the peltier effect, it's the same thing as this, just in reverse.
I don't have much experience with ROCm for large trainings, but NVIDIA is still shit with driver+cuda version+other things. The only simplification is due to ubuntu and other distros that already do the heavy lift by installing all required components, without much configuration.
