I have the same problem with oop. 10 levels of encapsulated calls just to see you were in an overridden methods without enough data to find out which implementation it was. Ugh
I don't get the cynism, I never implied any of those things. My heart to you on dealing with the trauma, really.
Most people on blahaj seem to have similar problems however and it makes for strange interactions, like this one here. I'm not sure how pointing out you probably were not thinking clearly in the comment above is bothering you so much. I mean, you're even the one talking about PTSD I reckon, not I.
Good luck with everything, hopefully you can read this before overzealous mods decide to delete it too.
I can just as well say that the screenshot above is the top 0.5% pushed by people trying to sell the tech. I don't really have an opinion either way tbh, I'm just being cynical. But my own experience with those tools hasn't been impressive.
That guy's probably one of the biggest name in deep learning. Obviously he doesn't write all those papers himself, he supervises research, like all professors...
I agree with your point, but you're arguing that noise can be redundant data. I am arguing that redundant data is not necessarily noise.
In other words, a signal can never be filtered losslessly. You can slap a low pass filter in front of the signal and call it a day, but there's loss, and if lossless is a hard requirement then there's absolutely nothing you can do but work on compressing redundant data through e.g. patterns, interpolation, what have you (I don't know much about compression algos).
A perfectly noise free signal is arguably easier to compress actually as the signal is more predictable.
It's funny because the money they send the US would partially be reinjected in the EU if they bought e.g. French planes. I'll never understand some of that decision making.
Ugh? That's not what it means at all. Compression saves on redundant data, but it doesn't mean that data is noise. Or are you using some definition of noise I'm not aware of?
Rust has a warning (has it been promoted to error? I think it was supposed to be) about comparing floats. Nothing to do with same being const. You basically don't have an equality operator for them
Then most people shouldn't be writing code, I don't know what else to tell you, this is probably one of the first thing you learn about FP arithmetic, and any decent compiler/linter should warn you about that.
I have the same problem with oop. 10 levels of encapsulated calls just to see you were in an overridden methods without enough data to find out which implementation it was. Ugh