WE hate O(n^2)!!

The solution is impressive, but considering that we write code for other people, it relies on a practice that, in my opinion, isn’t a good one. 99 is a magic number; few people will know what it stands for, making the code harder to understand and less readable.

genius

In this case a well designed class would have a field position which would be an ENUM e.g. Position.BOSS, Position.WORKER ... :)

no need to assign 0 to num. Instance variables gets default values.

It is not taken into account that there can only be one boss, if there are two people with the same name at a meeting and this name is the name of the boss, then we will get double scoring for both.

Is this faster?

I understood nothing, but guess it's clever)

True best practices

Go to stack overflow if you want to actively be unhelpful.

why isn't that helping? is that still the information you're looking for or something else?
ask specific things. if you failed to google, then google better xd - include the language, avoid special characters

Īn Java (and many other programming languages), ^ denotes the boolean "exclusive or" or "xor" function. A xor B is equivalent to (A or B) and not (A and B), or in English "one or the other but not both".

0 ^ 0 == 0
0 ^ 1 == 1
1 ^ 0 == 1
1 ^ 1 == 0