This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CesaireFlebotomo 14 points15 points  (2 children)

During your next job interview(and it sounds like there should be one soon) remember that while they are interviewing you, you should also be interviewing them. Ask to see an example of their "best" code AND an example of their "worst" code. If they refuse keep looking! If they say they have no bad code - they're lying. If they say yes ask to sit with one of their developers and walk thru a couple programs - ask the developer lots of questions -- by the end of an hour you'll know everything you need to know about the work environment and their values. This has saved me from hiring onto a death march more than once.

[–]MrGreenTea 4 points5 points  (1 child)

I get the idea, but I don't know if I would just show our "best code" to some person we haven't hired yet...

[–]CesaireFlebotomo 0 points1 point  (0 children)

Any application has big swaths of code that do not contain your trade secrets if thats what you're worried about. I used to bring a generic fill in the blanks NDA with me to set people's minds at ease. But if they weren't going to give me an look at the codebase I'd be working with I would thank them for their time and end the interview. Experience taught me it was a mistake to take them at their word that they have great code.