That's how to make a career. If you never make any mistakes, you're invisible. Don't do it too often though, or you'll eventually get promoted to management.
That's the main point I never understood about his voters. His political agenda and your political affiliation don't even matter. All you have to understand is that everything he does is for his own benefit. Nobody wants an egoist in charge in a smaller setting - why the fuck elect one as president?
Android has a good one that's simply called "Sleep". They track your movement and try to estimate light sleep in a set period before your actual wake time.
It worked pretty good in the past (not perfectly of course) but I've been waking close to my wakeup time for years now, so I just use it for tracking.
By definition AI (artificial intelligence) is any algorithm by which a computer system automatically adapts to and learns from its input. That definition also covers conventional algorithms that aren't even based on neural nets. Machine learning is a subset of that.
AGI (artifical general intelligence) is the thing you see in movies, people project into their LLM responses and what's driving this bubble. It is the final goal, and means a system being able to perform everything a human can on at least human level. Pretty much all the actual experts agree we're a far shot from such a system.
If you go back to my example, you’ll notice there is a UserUniqueValidator, which is meant to check for existence of a user.
Oops, right, I just glanced over the code and obviously missed the text and code had different class names. Another smell in my opinion, choosing class names that only differ in the middle. Easily missed and confusion caused.
I don't think our opinions are too far off though. You're just scaling the validation logic to realistic levels and I warn that in practice coders extrapolate too quickly and too often, which results in too much generic code which is naturally harder to understand and maintain than specific code.
I would argue that the validate routines be their own classes; ie UserInputValidator, UserPasswordValidator, etc.
I wouldn't. Not from this example anyway. YAGNI is an important paradigm and introducing plenty of classes upfront to implement trivial checks is overengineering typical for Java and the reason I don't like it.
Edit: Your naming convention isn't the best either. I'd expect UserInputValidator to validate user input, maybe sanitize it for a database query, but not necessarily an existence check as in the example.
Actually, our punishments for speeding are very mild compared to much of the rest of Europe. Going over the limit by such a margin will get you lose your license though.
No, he's addicted to Her.