Re:I will not hack on your codebase for free in an interview
by RBerenguel on Wednesday December 04, 2013 @11:00AM
(#6847719)
As redblackthree says below, there's some leeway in there. I guess it comes down to knowing what tradeoffs are you doing to get it done sooner. In my case I usually know where I've done some cheapish job and mark the code area with a "FIX: explanation of what should be done" for when I have time for that. I also eventually come back and clean up whatever code mess I got, or at least comment the mess so it doesn't come biting back at me in the future.
[ Parent
| on HN ]
There are no comments on this comment yet.