tiebreaker

You have to write code to remain an effective tiebreaker, but that’s where your coding responsibilities end.

So that's my tiebreaker: Microsoft's calendar platform is supported in more platforms than Google Calendar.

That is, scenarios where seeding couldn't be decided until the final (random) tiebreaker?

What I meant here is that you have to fix an occasional bug and ship an occasional feature, but only in order to remain an effective tiebreaker.

In the days of postcards the prize came from some sponsor, the TV production crew sifted the cards and found the ones with the correct answers, then picked out some quality tiebreaker.

In case of ties, there is no tiebreaker, so any orders that can't be filled at exactly filled at the clearing price are filled as much as possible in as close to equal proportions as possible.

The tiebreaker stuff is slightly different, and every candidate that gets a vote of confidence actually ends up chatting briefly with our CEO as the very last bit, which is more of a cultural fit thing than anything else.

You have to write > code to remain an effective tiebreaker, but that’s where > your coding responsibilities end....bug fixing js a fantastic way to stay in the code, and also show that most bug fixes don't require a re-architect.

Responsible for deciding overall system architecture (usually by acting as the tiebreaker when there're debates within the team), determining priorities, either assigning work or creating systems where the team can identify what needs to be done and do it, interfacing with their PM, pitching in technically when needed, and ensuring the overall engineering success of the project.

Even wikipedia unfairly lumps in Condorcet voting with its various "tiebreaker methods" - it's the tiebreaker methods that run afoul of Arrow's criteria, while the Condorcet method itself does not.

Similarly, if an election has a Condorcet Winner, and adding a candidate creates a Smith Set (thus potentially violating IIA if a certain candidate is chosen in a "tiebreaker"), this is not necessarily a bad thing.