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.

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.

deleted by creator

Different mindset. A user doesn’t want to find bugs but get shit done.

And we absolutely wanted to shoot the tester who gave us this use case.

Why? Because he tested well and broke the software? A user changing their mind during a guided activity absolutely is a valid use case.

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.

Yeah, the people at Pixar have no clue how to use a computer. Lol

Do you really expect their artists to be IT experts? You seem to be stuck in the early 90s mindset when “knowing how to use a computer” covered all disciplines.

But it can also be a matter of (inexperienced) devs just deciding, fuck it, I won’t try to merge it, I’ll just copy my changes elsewhere and throw away the repo.

Pretty sure that’s actually it. Git has a learning curve and, for example, some naive rebase not working out as intended can be scary if you don’t know what you’re doing.

It works well - for a Windows subsystem. It is well-integrated but also separate which can be annoying sometimes.

For example, you might code in Python in VSC against a WSL folder but make a script to eventually run in Windows. You need to install and update Python twice then - a Linux and a Windows version (obvious, but can be annoying).

WSL is also really slow, especially for filesystem heavy stuff. You know how on Linux programs sometimes run faster via Wine/Proton than on Windows itself? Yeah, this is the other way around.

It was earlier, when they released Windows 7 and it was the first (and only) release, management gave development a largely free hand and they could bring down some technical debt.

But apparently that didn’t work out for Microsoft and now we get one dystopian news after another.

Isn’t the POSIX incompatibility a major roadblock when scripting?

It must be a really deeply integrated part of the Windows kernel because it has never been able to show progress properly.

Back in the days of floppy disks it always felt that actual copying started when the progress showed 100%.

Makes sense. It’s like having your personal undergrad hobby coder. It may get something right here and there but for professional coding it’s still worse than the gold standard (googling Stackoverflow).

Onfuscators probably use it though, so no spec ever will be able to get rid of this crap.

BASIC. At least VB.