3 ms·
I don't get this though. At that point, the entire team had busted their bust and had actually met their goal. This guy basically took credit for the work that
by pyre 17y ago
I don't get this though. At that point, the entire team had busted their bust and had actually met their goal. This guy basically took credit for the work that the entire team had done in meeting the memory constraint. He just reserved some bogus memory so that at the last minute he could say, "Hey look! We've magically met the requirement! I'm a genius!"
- JacobAldridge 17y agoWhich is why the story is here as an example of "dirty coding tricks", and not as an example of "brilliant forward planning for coders".
- pyre 17y agoWell, when I read 'dirty coding tricks' I'm thinking 'ugly hack' not 'lousy cheater'. This wasn't some 11th hour 'patch the symptoms but not fix the underlying problem' story.
- 83457 17y agoI think the idea is to fool the team into 1) more quickly realizing their is a problem and 2) be less likely to come close to the requirement but fail. It is kind of like someone stealthily setting your clock forward 2 minutes because in their experience you have problems with punctuality.
- petercooper 17y agoThat's exactly what managers do if they have the foresight to pad a schedule.