With or without brackets?
With or without brackets?
Thought the same. Trivial questions are asked and answered all the time (more trivial than this one too, where the question to enter into Google isn’t even that obvious). When it comes to politically loaded topics people always like to swing the downvote hammer.
Get on your own lawn: touch ~/grass
deleted by creator
Since I generally prefer another serving of the main course over dessert, sure, I can just eat more lasagna for dessert.
How do you get 3 typos in the name when it’s actually shown on the image?
Since tomatos technically are fruit too, the text of that meme is still true but in a more boring way.
Advanced kit: add NoScript and block first party scripts by default. Works surprisingly well for visiting sites you don’t care about, just want to read the article etc. Just switch it off if you’re trying to buy something and get through the checkout.
Adnausem is built on top of ublock origin and will silently “click” on the ads behind the scenes to mess up your advertising profile and cost the advertisers money.
Tried it a couple of months ago. Didn’t nearly work as well as uBlock Origin, seemed buggy as hell.
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.
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.
I doubt most Americans would do that. I had American friends visit and they asked me to slow down at like 160 km/h.
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.
Mature/elderly people don’t care either. Nor do casual mobile players. Basically everyone except the former gamer populace plays these games.
I want to agree with you because that’s what I want too. Unfortunately, the financial success of f2p microtransaction infested pseudo-games tells the majority of players are just fine with that bullshit.
Earplugs were a game changer for my sleep.
Yeah, that’s what the commenter did but with extra steps.
Also, slouching every once in a while is actually better than keeping the same “correct” posture for 8 hours straight. We’re built to move.
Only of the attacker knows whether it’s a password or phrase. I’d argue that passwords are far more common and that’s what a cracker would focus on first.
As far as I know there still is no way to create actual randomness. You’ll still have some pseudo-random number generator and a hopefully unguessable seed. If you have “perfect knowledge” about that, cracking the password is almost trivial.