Lol. Maybe we can drown our enemies in paperwork.

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.

Harris might have a better chance

For sure. Good luck grabbing her by the balls.

He really is running low on soldiers, isn’t he?

I disagree. Scaled down to small and harmless it’s like handling kids. You explain what you don’t want them to do and what happens/you’re going to do if they continue. Now it’s crucial you go through with what you threatened them with.

If you either don’t deliver on the “threat” or don’t act as you said you would, guess what happens? They just continue or it even gets worse.

Of course it’s more delicate/difficult when handling with powerful and intelligent adults but it’s at least similar. Not issuing threats is just not communicating. If you then just act (violently), things are more likely to escalate.

Edit: or back to the kids analogy: don’t tell them anything but smack them once they went too far: may help in that instance but they’ll just learn to better avoid you and do shit behind your back.

Also whole degrees. edit: no, that’s wrong, there are thermostats that allow 1/10th of degrees (I only have old manual ones). Still, you probably are not able to tell the difference between 20 and 20.1 °C. Humidity is far more relevant.

A difference of 2 °F is 1.1 °C…

Always? That’s my first reply. Bug of what? A flaired character has a different code than a standard one, so your files would be incompatible with any established tools like find or grep.

For traffic Celsius is more intuitive since temps approaching zero means slippery roads.

You’re long passed that with Fahrenheit. And on a scale from 0 very cold to 100 very hot, 32 doesn’t seem that cold. Until you see the snow outside.

They didn’t say a difference of 1K isn’t significant but the difference of 0.1K isn’t.

And since the supposed advantage of Fahrenheit is that it better reflects typical ambient temperatures, we have to consider relevance for average people. Hardly anyone will feel a difference of 0.1K.

That’s why European weather reports usually show full degrees. And also our fridges show full degrees.

I don’t like that approach. Text search won’t find all the different possible Unicode representations.

If you’re afraid of triple letter agencies you probably shouldn’t engage in social media at all.

The privacy concerns are about coercion from the user base. The bar to spin up a private instance to get to the voting data is far too high for 99% of the users.

If it’s effort, virtually nobody does it. Convenience is king since the beginning of the internet.

Tells me all I need to know about what the method does

No, it only tells you what the method is supposed to do.

While that may be helpful it may also be misleading. It helps just as much as comments when debugging - and that probably is the most relevant reason for trying to figure out someone else’s code.

Most are but Jever Fun is not sweet at all. It’s not as bitter as the original Jever but also not sweet. I don’t wanna call you a liar too but maybe you remember another brand?

In the long term it works quite a bit better as a valuation tool. Bubbles tend to not last very long.

Basically lower and upper end of sizes, yes. Team sizes too.

Worked with both, both worked fine.

deleted by creator

I wish it was friendlier to Nvidia

You got that one backwards.