A friend of mine was applying for a job where they required "at least 5 years knowledge with Angular version X.Y.Z" (can't remember the exact version, but they asked for all three numbers).
He said "I've got 7 years of knowledge with version X-2 to X+2".
The HR person was like "But you don't have 5 years of knowledge with version X.Y.Z, so you don't fit for the job".
The real fun part was that version X.Y.Z had only been out for two years at that time.
It's nature's Beast of ARRGH
I've seen a 3DS in the Technical Museum in Vienna.
Nice!
If JS is chaotic neutral, what then is chaotic evil?
All I'm saying is
"10" + 1 => "101"
"10" - 1 => 9
"a" - "b" => NaN
I recently joined a team that had no backender for a year and the frontenders maintained the backend. In this case the image totally applies.
I once had a company give me an assignment that sounded very much like what you are describing. They said I should allocate 10h at once to implement a real-life task that they had and that their developers "already solved".
At that point I only wrote a handful messages with their recruiter and hadn't even spoken to a human there. I didn't even know anything about the team, my potential boss or the project at that time.
I didn't even answer back, just ghosted them. I'm not going to spend multiple hundreds of Euros of my time just for some assignent to maybe qualify for an interview.
90% of the things that Japan introduced according to comment sections on the internet never happened (or never made it past the prototype stage) and the rest was actually introduced in Korea, not in Japan.
The Japanophilia is strong with a lot of people on the internet.
There's this idea I've been considering for a long time.
Imagine putting a remote controlled firework smoke bomb under the tailpipe, hidden from sight. At best a really stinky one that smells like burned rubber or something.
When someone follows to closely, just fake an engine issue or something by activating the smoke bomb and fill their AC air intake with the smell of burned rubber for weeks. Just to teach them to not follow too closely again.
You always have to balance: Do you want the user to have "some" user experience, or none at all.
In the case of image viewers or browsers or stuff, it's most often better to show the user something, even if it isn't perfect, than to show nothing at all. Especially if it's an user who can't do anything to fix the broken thing at all.
That said, if the user is a developer who is currently developing the solution, then the parser should be as strict as possible, because the developer can fix stuff before it goes into production.
This is literally the difference between me and my wife ;)
Well, IRL hacking doesn't have exciting gameplay mechanics. So more realistic hacking game might not be such a clever idea.