Would you? Actually, yes. Getting fired means that (at least in principle) I've done something "wrong" but under real-world conditions, and with no artificial

Would you? Actually, yes. Getting fired means that (at least in principle) I've done something "wrong" but under real-world conditions, and with no artificial clock. So if things get bumpy (as they inevitably do in real environments, at one point or another) I have ample time to actually talk to someone and try to right things before they slouch further. And in any case, if it happens I'll almost certainly know why. (Unlike LC where it's always "OMG I only have 5 minutes left. Should I check the logic in this corner case or clean up my code bit? How do I know what my reviewer would rather see? Since they're hiding from me there's no way to know.") But "failing" LC just means... I've failed some make-believe test under completely unrealistic time pressure, perhaps under criteria that will never be revealed to me. Which was assigned to me because someone had a vague idea that this is as good of a proxy as they'll ever be able to come up with for real-world programming ability. Oh and unlike LC -- at least I get paid for my time. And will most likely be learning things infinitely more interesting and useful than what preparing for LC teaches me. For that and a bunch of other reasons I greatly prefer trial periods.